This is not something I would leave to Time Machine. Get palettes scrambled. Switch to palette that is correct for the working environment. Quit VW. Replace scrambled workspace with backup. Restart VW. Next time you are in environment needing the other workspace, open VW and switch to it. It should work just fine on Mac. When I am good enough to remember to do this it works fine for me.

I think this has been wished for many times. Rather than waiting for someone else to wish it, go the the Wish forum and add it yourself so we can vote it up. The best work around for this is to put you workspace folder somewhere accessible (maybe a shortcut on the desktop) and make backup copies of your multi-screen workspaces. That way when you open VW with the wrong workspace you can simply change workspaces and replace the scrambled one with the backup. Or just continue to be lazy like me and just deal with move palettes all the time. ;-)

My understanding is that there is no Restore Palette Positions option. Effectively, the Save Palette Positions is primarily there to force things to save in case there is a crash. You are right, when you change the workspace or when you do a normal quit of VW, the palette positions are saved automatically. So if you mess up the palette positions, your only option is to force quite VW. Then when you reopen VW, the palettes will be back to the previous saved state. I hope that I am wrong about this and the @JimW will correct me in the morning.

Bruce, This is back to the idea of "Container Objects". Every object in VW has a class and is either on a layer or in a container (that is eventually on a layer). Symbols, Groups, Marionette Objects, and Plug-in Objects are all examples of container objects. In order to see objects inside a Container Object, then the Class of BOTH the Container and the Contained object must be set to visible. If you have multiple nested Container Objects, then the class of every Container and every Contained must be visible. Since you want to show a symbol in different classes, the objects inside the symbol (container) will at some point be in a different Class than the symbol. This means that you must have at least two classes visible to be able to see them. Your VW expertise and level or drawing detail have progressed to the point where the Class Option of Active Only is no longer going to help you very often. Congratulations and Condolences. You are going to have to either adjust how you are drawing or allow you to continue to use Active Only (basically meaning no use of Container Objects) or change your workflow to allow you to accomplish something similar to what you used to get with Active Only. The best work around for something similar to Active Only I have found is to leave the Class Options set to some form of Show Others and to make every Class invisible. Then set either the class of the Container or the Contined Objects to visible depending on what makes more sense for what you are working on. You can then use the Command Left Arrow and Command Right Arrow to step though the classes. Since the Active Class is always visible, that visibility coupled with the Classes that you manually set to Visible will simulate Active Only. If you do this often, you can use a Saved View to set the Class Visibilities the way you want. It is often better to try and keep as many of your container objects in a single class (often the None Class) as possible. That way when something is missing you only have one (or a few) Container classes that you need to be concerned about in trying to find things. Another option is you only have a few of each symbol in a drawing, especially if what is included in the symbol is a single object, is to edit the Symbol Options and choose the Convert to Group under Other Options. This will let you save the object as a Symbol so it will show in the Resource Browser and be accessible from multiple drawings (Library File) but will place it in the drawing as either a Group (if there are multiple objects inside the symbol) or just as an object (if there is only a single object inside the symbol). If it places as a group you still have to worry about Container/Contained classes, but if it is placed as a single object you don't as there is no longer a container. I'm glad you found a solution that works for you with Layers. Like I said above, you probably need to adjust your workflow to your enhanced drawing skills.

I am not enough of a Windows guy to know, but that path does not sound like a separate Windows 8 Users account. Try a totally new Windows user account.

I think you could either zoom in and nudge them just a fraction. or possibly resize them so they are a very small amount (say 0.1mm, 1/32") smaller. In Top/Plan you could do the offset so they are ever so slightly not in the same plane. Not what you wanted to hear, but my best suggestion.

Definitely sounds like a computer problem not a VW problem. Can you try creating a new user account and see if the problem follows to using VW in the new account?

There have been some discussions in the past on some type of developers group, but never any real movement. You might find that more of the people you are interested in working with may hang out on the Vectorscript-L mail list rather than here. http://www.vectorworks.net/community/mailinglists Regards, Pat

What is officially available is located here: http://www.vectorworks.net/support/custom But that is only current through VW 2015. Try contacting your sales contact and ask them to send you the following documents so you can do a full evaluation before purchase. Hard copies have not been available in a long time. You will have to print yourself. The Function Reference is a hyperlinked document and would be "interesting" to print into a useable format. Vectorscript Function Reference as HTML Vectorscript Function Reference Appendix as HTML. You want to versions of all of the above from the VWHelp folder in Applications/Vectorworks 2017/VWHelp/Script Reference. You want the entire Script Reference folder. The Vectorscript Language Guide is available for download from http://developer.vectorworks.net/index.php/VectorScript#Language_Guide. But his has a copyright of 2013 so it is a little out of date also. There are a number of useful things on that same page/site, but again they are mostly for VW2015/2016 so not the most recent. I used to use the online version of the function reference, but have switched to the local both for speed of access and to have the most recent info, but I still access developer.vectorworrks.net to check out the annotated function reference if I am having trouble. Hope this helps. Pat

I think the Vectorscript function you are looking for is ModelVecToScreenVec. I am not on a machine with VW right now, but it is very possible that this is not a standard Node, but it should be fairly easy to make a custom node for it. There are also a number of other VS functions for converting Working Plane to Screen Plane. Search the Function Reference for Screen.

Vectorscript is still available and has not changes a lot. There are a number of old calls that have been depricated, and a huge number of new things added. Most of the people who were around at VW8 are still around. The developer community is not huge, but it is very helpful. Python is also now an option. It uses the full python with effectively a library into the vectorscript calls. Lots of options if you can deal with Python. Marionette is a graphical scripting language. The individual nodes are written in Python, so you can extend as you see fit. The full SDK is still in C/C+/C++ etc. It all depends on what you want. I would guess that you could open a VW8 file in VW2017 and get most scripts running in just a few hours. I did something similar for a client a few years ago. Took some research to find the critical differences, but I was able to convert a suite of programs containing about 5000 lines of code in about 8 hours.

For at least some of the criteria, you can use a Starts With option instead of an IS condition and it will automatically generate the criteria with the asterisk. As Michael says, it does not work with Layer Names. :-(

Perhaps this one is closer to what you want. It will rotate all visible selected objects by a random amount between 0 and 90°. If used inside a group (edit mode), only the selected objects in the group are rotated. If used inside a Symbol Definition (edit mode), only selected objects inside the symbol definition are rotated. Test on a backup copy to ensure suitability before using on an active work file to ensure you understand the performance. Procedure RotateRandomEachObject; {Rotates each selected object in the active layer a random amount <90°} {Works on selected objects in a layer, symbol definition, or group} {Symbols and PIOs are rotated around the insertion point} {Other Objects are rotated around their center point} {© 2007,2008,2010 Coviana, Inc - Pat Stanford pat@coviana.com} {© 2017 Pat Stanford pat@coviana.com} {Licensed under the GNU Lesser General Public License} {No Warranty Expressed or Implied. Do no operate motor vehicles} {while using this script.Side effects include baldness and acne.} Var X1,Y1 :Real; Procedure WithIt(Hd:Handle); Begin If ((GetType(Hd) = 15) or (GetType(Hd)=86)) then GetSymLoc(Hd,X1,Y1) else HCenter(Hd,X1,Y1); HRotate(Hd,X1,Y1,(90*Random)); End; Begin ForEachObject(WithIt,((InSymbol & VSEL=TRUE))); End; Run(RotateRandomEachObject);

It sounds like perhaps you are doing your dimensioning on the Sheet Layer directly, not in the Annotations Group of the Viewport. The Sheet Layer always has a scale of 1:1. If you set your viewport scale to 1:1 then you can just use the dimension tools and get everything to work. When you change the scale of the viewport to something other than 1:1 then your dimensions are incorrect. Instead, right-click on the viewport and choose Edit Annotations. Put your labels and dimensions there. The Annotations Group is at the same scale as the viewport. That way if you need to change the scale of the viewport, the dimensions will scale also and retain the proper values.

The problem was likely that the layers were in different views. It has been such a long time since I worked without Unified View I had forgotten that requirement. Unified View basically makes sure that all the layers visible are of the same scale and same view. If you change the view on a layer, all the other layers switch also. With Unified View off, you can end up with one view in Top and another in Front.