C. Andrew Dunning

In Developer mode the code gets totally re-processed each time the tool is called. Are you running 4K monitors? If so, make sure you are running the most current VW2026 update. There was an issue early-on that should be rectified in the current build.

@Ben Garcia - Sheesh...I can see why you are frustrated. I would be too!!!! I opened your file in both 2025 and 2026 and am not seeing the sorts of delays you are. I also tried the same configuration with the Landru Design version of the tools - in both your file and in a fresh one. Would you check/try 2 things:? Please be sure that you are not running VW in "Developer" mode ([Tools][Options][Vectorworks Preferences...][Session]). Make sure "Run scripts in developer mode" is NOT ticked/checked. Having this box checked will cause the sort of slow-down you are seeing. Most users never tick this box but it is worth at least checking. With VW NOT running, would you find your "SavedSettingsUser.xml" file and move it to a safe place. Restart VW. Please a S.A. instance and open the Configuration dialog. Is it now a usable size?

If you would post or DM me a copy of a file containing the array/configuration that is giving you issues I'd be happy to take a look. Intricate tilted Symbols continue to be a challenge but default Symbols and Library/Catalog objects should be similarly fast. As to the posts to which you linked, they are 3-4 years old and, while there is admittedly room for improvement, many of the concerns/requests have been addressed in recent builds.

Yup. Edited.

SetObjectVariableBoolean(1160,HANDLE,FALSE) will set an object to the Layer Plane and SetObjectVariableBoolean(1160,HANDLE,TRUE) will set it to the Screen Plane.

If you've been following this thread and missed the announcement, we just released a SoftGoods 2 version that answers the concerns raised here:

If you are following this thread and missed the stand-alone announcement, we just released a new SoftGoods 2 version that addresses the questions raised here...:

Merry Christmas from Music City, USA! We trust that 2025 has been good to you! We have just released version 2.55 of SoftGoods 2. In addition to a fair amount of "under-the-hood" refinement, this update includes 2 new Pipe-and-Drape features that have been on multiple users' wish lists for a long time: Non-Sleeve Drape mode: Provides for the modeling of configurations that use drape that straddles uprights, such as offered by Wentex® and others that use hook-and-loop material (like Velcro®) or ties instead of sleeves or pockets. Bottom Drape Height: Allows for the easy creation of "arched" entrances and exits. If you are one of our current users and purchased either a SoftGoods 2 or Producer's Pack 3 license since September 10, 2024, this update is available free-of-charge and your latest link, password, and key are still good. Reach out if you have any issues. For everyone else, see our Plug-Ins page for more information. Have a great Christmas!

100% my pleasure!

Edit the Symbol definition. In the attached "VS-ModData" Record, enter "Mirror-Above" in the "Sub Type" field. Does that work??

Would you post a file containing the Symbol you are trying to use?

@SamIWas, echoing some things @Jesse Cogswell said...directly and indirectly...and, in this thread and the one you cited: Use version-tracking software. In addition to having pre-change back-ups, this will allow you to track WHAT changes you made and WHEN you made them. This has saved my bacon MANY times over the years. More than once I've worked on something for a day (or two) and decided to revert to the pre-change state. And...I've been able to find a change I made "last week" or "two years ago" - either to undo something or to remind myself what I did and why. Code/develop in the oldest VW version you "sanely" can. This might open sales up to more users and can help in protecting yourself from encryption mistakes. For example, currently the oldest public release of our tools is VW 2023. I do all of my development work in 2022, copy duplicate VSO/VSM/PX files to newer versions, and only encrypt in 2023 and newer. So, I always have "safe" files. Another thing that this does for me is that, if I have issues with a given version, I can report to the Mothership things like XXX call working fine in 2022-2025 but not in 2026. Just food-for-thought...

A little late to following up on the conversation but... Our system is based off of the last 6 characters of a user's VW license - which are submitted at the time of purchase. A 16-character key based on those characters is sent with package download information. Our current offerings are comprised of 15 Tools (+ a few utility Commands) that are distributed in 8 different packages and an "all-in-one" suite. The key system "knows" which of the tools a user has licensed (and, added at a later time). 1 key might enable 1 or more tools and/or multiple keys can be entered at different times. The first time a user uses a given tool he/she pastes/enters the key, which is then stored in the Saved Settings file. For each VW session, the first time one of our tools is used a hidden Record is created (or, re-created) and toggles are added based on the user's VW license and the Saved Settings entry/entries. Subsequent uses of our tools in that session check that Record to enable Parameters/functionality. The has been a pretty solid system. Now that we've been using the system a while, the only issues we tend to see have to do w. VW license typos, mis-matched license #s, users sending us old key characters instead of VW license characters, or mis-entered key characters instead of copy/pasted keys.

I do all of my parameter visibility and enabling calls in the 41 event. Missing or bad key: License button made visible and all parameters are disabled. Good key: No License button shown and parameters shown/hidden/enabled/disabled per appropriate values/settings/etc.

Resurrecting this thread as I'm thinking about future tool enhancements... For P&D applications that "bridge"/"span" uprights, do all of the panels simply Velcro to one side or the other of the horizontal sliders? If not, how do the panels attach to the horizontal sliders? Tie on? Photos would be helpful. Where in the world is this common - if "common" is the right word? Thanks!