Jump to content

Peter Vandewalle

Distributor
  • Posts

    319
  • Joined

  • Last visited

Everything posted by Peter Vandewalle

  1. Marionette nodes need to be coded inside the node. No further interface needed. Are you sure you need to create Marionette nodes? Or do you need to script just Python. For Python scripting we use Eclipse.
  2. Did you (have to) rescale the file after the import? That could cause the linestyles to be too small and hatches be too dense also. Try to never rescale an imported dwg, rather import again (in a new file) using the correct units.
  3. For the hatch not printing: any object really far away from the internal origin? That causes all kind of graphic issues. For the linestyles not showing: what scale is the design layer?
  4. I would do that text editing in Python. That way you could keep it all in one Vectorworks command...
  5. If the script is a menu command, you could also use the menu command parameters...
  6. =runscript(scriptable, par1, par2, …) In the script use WSScript_GetPrmInt(index) te get an integer parameter. Others get real, text, image.
  7. Would it solve anything to store your workspace in a workgroup folder. Then you wouldn't have to redo all the work after deleting a user folder? That's what I do with all my python plugins and workspace...
  8. @WhoCanDo Did you migrate your workspace from 2021 to 2022?
  9. @WhoCanDo Are you in 2022 or in 2021? I see the repeat last command isn't in 2021.
  10. Parent PIO is a node in the Marionette defaults. I think it has been added later. I've been using it for a few versions now.
  11. The Repeat Last Command and Recent Commands are also under the right click menu, BTW.
  12. Years ago I used to do that with Applescript. But since the interface changed, this became impossible...
  13. In Python: vs.SetObjectVariableBoolean(_hObj, 684, False) # Text has no tight fill Vectorscript should be: SetObjectVariableBoolean(_hObj, 684, FALSE);
  14. Just thinking out loud… I suppose that if you use a database list of the doors with INSYMBOL, the handles are referring to the door in the symbol definition? And the x and y position values also? If that’s the case I’m afraid we’re running into the limits of worksheets…
  15. I think runscript would be able to do this. Once you get the handle to the door object, go for the parent object to get the symbol. Could that work?
  16. I would use a ForEachObject with criteria selected is true.
  17. Or use saved views to turn off the layers you don’t need when working at another scale?
  18. Since unified view exists, I never turned it off. Different scales shown together is done in sheet layers… Or am I missing something?
  19. Move a resource to a folder: I think SetParent()…
  20. Documentscript with Message(GetTypeN(GetObject(‘textstylename’))) will get you the answer.
  21. You can make database formulas smarter by using a "Databasebyscript" formula. Of course you'll need to script the list of shown objects yourself.
  22. Pat is right. But I think a script could make it semi-automatic. If the worksheets have a name beginning with something recognizable, you could select them, get the instance layer and update the database formula. Also, have the layer name in a cell and have the database formula use that cell as a reference. Like “(L=A1)”. That’ll make it easier to update your worksheet.
  23. Libraries are always version dependent. You’ll need a folder by version, just like the user folders.
×
×
  • Create New...