Sebastiaan

Make sure the unified view is on. It is in the view menu

What helped for me in some cases, not al unfortunately. was to go into the edit 3d components of the truss symbol. And to move the geometry there for instance 1mm in 3D. This would force the geometry to appear again in OpenGL. Then I edited 3D again and moved the geometry back 1mm again. hopefully this helps a little bit as a temporary workaround.

the function already exists in Data Tags. It’s called a dynamic text field and I would really want to be able to use a dynamic text field in Label Legends!

there is a new workflow for multicell fixtures in VW 2021. You can find explanation about the new function here. https://app-help.vectorworks.net/2021/eng/index.htm#t=VW2021_Guide%2FLightingDesign1%2FConcept__Multi-cell_lighting_devices.htm&rhsearch=Multi cell&rhhlterm=Multi cell&rhsyns=

Hi All, I am trying to get my head around manipulating accessories through Python scripts. Ultimately I would like to be able to position an accessory by a criteria such as the accessory name. I wonder if that is even possible as the function reference only seems to give handles to accessory index and not the name, but that is for a later step. As a novice on scripting I am getting stuck on getting the GetAccPos3D & SetAccPos3D to do anything at all at this moment. First I tried GetAccCount which worked instantly: crit = "((R IN ['Lighting Device']))" def callback(h): NumAcc = vs.LDevice_GetAccCount(h, 0) vs.AlrtDialog(NumAcc) vs.ForEachObject(callback, crit) Then I tried GetAccPos3D, and the script seems to run but does not do anything. I tested the ForEachObject with a test string in an Alert dialog in the Callback, so I am sure that this does step through the lighting devices. Also I tried various combinations of the Accessory index and Cell index, but to no avail. My assumption is that a single cell lighting device would have cell index 0, and in the OIP I can see that the Accessory I am trying to manipulate has #2 as prefix before it's name in the dropdown. So I assumed that the accessory index is 2. Nonetheless I tried many other combinations as well. Also I am uncertain on how to handle the fact that this function returns multiple values. crit = "((R IN ['Lighting Device']))" def callback(h): outRotation3D, outPosition3D = vs.LDevice_GetAccPos3D(h, 0, 2) vs.AlrtDialog(outRotation3D) vs.AlrtDialog(outPosition3D) vs.ForEachObject(callback, crit) Would anyone be able to push me in the right direction?

For Universe and address field since VW 2020 there is the ‘Universe/Address’ Field that Automatically combines the two fields together with a separator. You can change the separator if you like in the spotlight preferences. for other fields I recommend the AutoplotVW plugins. It has a menu command called ‘copy field to field’ that will do what you want.

I do agree with this! Please give the option back to us. This has saved many hours of work getting viewports from one file to another. You do not have to advertise it as a recommended function. Just let us use it as the workaround that it was please?

There is no dropdown there. You need to click on the word none in the row of the field that you want to add the container to. Click until it reads the desired container name. when you open the Label legend Manager for the first time 4 default containers are automatically added to your document ( circle, triangle, Rectangle and hexagon). They are placed as 2D symbols in a folder named Containers in the recourse manager. if that is not the case in your file you could try to open a new file and open the LL manager and then import the created container folder with it’s contents to the file you are working in. Also you can create containers yourself. If you crate a 2D symbol and place it in the folder named Containers, it will then become available to use in the label legend manager. The insertion point of the containers 2D symbol will be placed at the center point of the text field that you apply it to.

Really interesting Pat! Thank you! I will now spend my time trying to actually understand what the code does.

Interesting! Although as I’ve only just plunged into the the world of scripting in VW, I might need some more practice until I attempt that!

I’m curious what Pat meant with that too!

Good idea to use the wildcards. That might make it shorter indeed. I will look into that. I do want 100 to belong to the 1 -> 100 range, but that shouldn't be too hard to fit in. I was trying to find some information on the database by script function and did not see much information about in. But I am curious what it is.

Yes I was guessing that too. It also kinda makes sense when you think of it. There is no cell to represent as value. The function does not change the original database and would have to create a new list of the fields as number values which obviously it doesn’t. I already have the workaround so it is what it is. At least I now know it’s not just me. thank you!

Hi Raymond, The issue is that I think that the value function does not work as expected when used in a DB formula. So your proposed formula does not do the trick either. Thanks!

Hi Pat, Of course, attached is a file with 40 lighting devices. 20 of them have the channel field filled with numbers from 1 to 20. the other 20 have numbers in the channel field from 101 to 121. Very curious if this will work in a DB formula. DB Formula Value Fun.vwx