Search the Community
Showing results for tags 'lock'.
Found 3 results
Hi All, I have a client currently who enjoy the concept of the Project Sharing features although wish for them to be used in a more global environment, unrestricted to a project file. They have quite detailed plans of their venues with specific things which should not be moved (diagonal bars, fixed height winch bars, fixed curtains, fixed orchestra pit deads, etc.). Commonly they will send these plans in the .vwx format to either external suppliers or prospective hirers who will send the plans back months later with their proposed changes. The problem is that often these external users will send back a plan with modification to the specific items above (moving grid pieces to locations which do not exist and/or places which have other obstructions, moving the pit to invalid stopping locations, etc). Often these changes go unnoticed until bump-in periods where conflict occurs as both parties believe they are in the right. The ideal would be the ability to password lock layers within the file. The ability to lock the 'Grid' layer for example and restricting the editing functionality, yet still allow class switching. Should the user need to move something in this layer they call in, receive the password and the file is logged with a change to that layer (possibly within the project sharing History). I'm aware we have referenced layers as an option although this has been tried and still required either a) releasing a second reference document or, b) the reference being broken and edited anyway. @JimWlet me know if I'm missing something here. Otherwise wishlist? Hope you're all well, J
I created a plugin object using python. The main code was pasted into the script editor via the plugin manager. I compiled the script and the plugin item works as it should. Now I would like to lock the script. I'm on a mac and recently made the jump from Vectorworks 2008 to 2016. In the past when creating a vector script I could lock it by holding down 'command' + 'option' + 'shift' + 'caps lock' (it was important that all external files had the extension .px) Now i'm in 2016 and scripting with Python. I only have 1 other file in addition to "import vs", which is, "import shapes" when i compile my script (shapes.py). It finds this file via the scripts options/environment paths. How do I go about locking or encrypting this plugin object? also, I do have a __init__.py file included in the folder that contains shapes.py
I saw a couple threads concerning locking the palettes in place so that they can not move using multiple monitors. I did not see anyone answer the previous questions. So i thought i would ask again.. Is there a way to lock your palettes when using multiple screens. So that they can not be moved.