Antonio Landsberger

Unfortunately doing it this way is pretty bad performance wise, rather than initially filtering by the active layer within the Objs by Crit node. That's why an OIP checkbox for "currently layer only" would be nice as an improvement of this node.

@Johannibal Check out this awesome python script by @Takeshi_Kimura I just tested the python script in Vectorworks 2026 and it still works flawlessly in a new empty document with the scale of 1:1.

Yay, nice. Thank you. 🙂 That makes perfect sense!

Ah, so you have to run it twice? Is there no fix?

Where could be the issue? Since it's a single node I post both the document and the code here: Write symbol names in worksheet.vwx @Marionette.NodeDefinition class Params(metaclass = Marionette.OrderedClass): #APPEARANCE #Name this = Marionette.Node( 'List all symbol names in worksheet' ) this.SetDescription( 'Running this node will first create a worksheet, then fill it will the names of all symbols in the resource manager.' ) def RunNode(self): import os HSFPath = vs.GetFPathName() FileName = os.path.basename(HSFPath) WorksheetName = FileName[0:-4] #script resourceListID, numItems = vs.BuildResourceList( 16, 0, '' ) WorksheetHandle = vs.GetObject(WorksheetName) if WorksheetHandle == None: vs.CreateWS(WorksheetName, numItems, 1) #{Save the current AutoRecalc state} autoRecalcState = vs.GetWSAutoRecalcState(WorksheetName) #{Turn off worksheet Auto Recalculation} vs.SetWSAutoRecalcState(WorksheetName, False) for cnt in range( numItems + 1 ): vs.SetWSCellFormulaN(WorksheetHandle, cnt, 1, cnt, 1, vs.GetNameFromResourceList( resourceListID, cnt )) vs.SetWSAutoRecalcState(WorksheetName, autoRecalcState) vs.RecalculateWS(WorksheetName)

As I understand it: The active layer will be set to the chosen visibility.

For layer visibility there are HideLayer ShowLayer GrayLayer

Exporting Marionette networks (particularly big ones) as Python results in a convoluted mess of variables. I don't believe, that kind of code is suitable for creating plug-in objects.

Does anyone know, what exactly this image is depicting?

@Marissa Farrell Could you please look into this? A conversion is ok, as long as the original object is left in place and the new object is just temporary.

Here's the new link: https://github.com/Vectorworks/developer-scripting/blob/main/Function Reference/Functions/vstGetEventInfo.md in case someone stumbles upon this entry like I did.

Hi @nbakovic What you want is either an event triggered script run, which Marionette and scripts have no access to or knowledge of, or a script that runs in certain intervals to check for changes. The latter is also not possible, because that would essentially be a script running in the background, but Vectorworks is always blocked during script runtime, thus there could also be no change to check while the script is running. You could create a menu command (from a Marionette wrapper), that shows you the relevant information you want to see - no matter where in the document you are. It could even be information from different objects and records (all in this one message).

@C.T Please refrain from cross-posting this question across several unrelated and years-old threads. Thank you. Create a new one instead.

Benson, In general when it comes to scripting and objects in Vectorworks, I would advice everyone to first do all computations mathematically and then move or create objects in the drawing pane. With 2D and 3D loci I would simply set new coordinates (after the calculation) using the Move node.

"Angles are in Radians" has already been reported (https://jira.vectorworks.net/browse/VB-169146) a while (almost 5 years) ago.