Pat Stanford

It should be possible to create a list of the classes and visibilities for a viewport. But it will probably require a script to create the list. The easiest way to format the list would be to have the script create a worksheet. Are each of your sheet layers a single viewport? Do you want the list to include ALL of the classes in the file and their visibilities? Or would just having the classes that are visible or grey be sufficient? Tell me more about what you want in the list and I will see if I can find some time to develop a script.

You will probably need to contact customer service by phone on Monday. If you are not in the US you will need to contact your local distributor.

PeterT's idea would probably work by putting the Plugin and Workspace folders on something like DropBox. I would probably leave the real folders where they are and put an alias/shortcut in the Dropbox folder. The problem with this is that you don't really control the distribution. If someone who is using the folder adds or deletes a plug-in or workspace, then that will be broadcast to everyone. Does not give you as much control to be able to determine who can use what. I don't know if there will be a problem about parameters being over written by effectively sharing a single folder. It could be annoying to have a wall set to a certain set of parameters and either in the middle of using it or the next time you restart VW having them be completely different. If you are going to try this test it thoroughly before you do a full roll out.

This should give you at least a starting point. I have written 2 PlugIn Objects (PIOs). For this purpose PIOs are nice because they easily handle the user interface of getting the length you want the object to be and setting up the OIP (and the Tool Parameters) to allow you to set the Jam, Sash and Leaf depths and widths. It also makes the math very easy as internal to the PIO, everything is done in local, unrotated coordinates. VW then handles the translation to real world coordinates. Put the attached VSO files into your user folder/Plug-ins. In my case on the Mac, this is in User/My User Name/Library/Application Support/Vectorworks/2017/Plug-ins Once the files are in the right place, I think you have to resort VW for it to notice them, then you need to edit your workspace to add the new tools to a tool pallet. The tools should be in the Miscellaneous category. Once the tools are in your workspace, just select the tool and draw a line. The first time you run the tool the Parameters dialog box will open and you can set the defaults. You can change them later by clicking the Setting button (crossed wrench and pencil in the Mode bar). After closing the dialog box, just draw a line and after clicking on the second point it will be replaced by a door or window. The object is drawn with the Jams centered on and contained by the drawn line. If you would rather draw on the edges or have the Jams drawn outside the PIO line, changing the coordinates in the PIO scripts is relatively easy. Similarly, all the objects are drawn using a fill of NONE and the currency active drawing attributes. If you think some of the objects need different colors or line weights, the script can be relatively easily changed to allow that. Let me know what you think. Simple Door 2D.vso Simple Window 2D.vso

Was there supposed to be a link to the instructions you are trying to follow? In general, any Record.Field information that is displayed in a worksheet is automatically 2-way. Chang the data in the OIP and recalc the worksheet and the new data will show up. Change the data in the worksheet and the data in the OIP (and the object itself if the data effects how the object is drawn) will update. This only works on fields. You can't use this for calculated information in the worksheet (things like =Area, =XPostion, etc.) This works with both user created records and with PIO records.

I think the search is rather hidden. I had to ask about it originally also. Note also, that the disclosure triangle at the left side of the search box lets you to to an advanced search mode.

Try switching to a different workspace.

The Data Stamp tool has the ability to place the file name on the drawing. In the Designer workspace this is in the Dims and Notes tool set. You will have to select the object and click Update in the OIP if you save the file with a different name.

Where all of the layers in the same view? Did you Align Layer Views before selecting and moving? Was Unified View turned on? If a layer is in a different view say Top instead of Top/Plan, then you will not be able to select the objects on that layer.

Restart VW? Restart Computer? What operating system? When did you switch to VW2017? Do you use a custom workspace that has been imported from a previous version? If so, try editing the workspace and remove and re-add the Ungroup command and reattach the shortcut.

The ALT Codes are an operating level service, so I doubt there is much that VW can do about it. I don't think VW ever sees the ALT codes, just the character that the operating system returns. I would start with a web search on Alt codes for Win 10 as a starting point. http://www.worldstart.com/alt-keys-not-working-in-windows-10/ was the first hit.

If you are looking for data from a PIO instead of a symbol you need to use the PIO Record and Field information. This can be hidden or use different names than are displayed in the OIP. The script in the attached thread will give you a list of all of the fields in the PIO record. Place an instance of the PIO in a drawing (not inserted in a wall) and run the script. The resulting worksheet will have the information. Make sure you get the latest version at the bottom of the thread.

Are you using the same fonts in each version? If not, it is probable that you are using a font in 2017 that does not support the additional fractions.

There are currently no great VS learning resources. There is some information on developer.vectorworks.net This includes the Language Guide and an old version of the Function Reference that has some annotations to it. The Function Reference is located in the VWHelp folder of the VW2017 application folder Vectorlab.info has some interesting information. Probably the best learning resource is this forum. Just search on function or procedure names that you don't understand and see how they have been used by others. Ask lots of questions. Take a look at the old Archive:Resource Share-Vectorscript forum for lots of good resources. https://forum.vectorworks.net/index.php?/forum/28-resource-share-vectorscript/

Select the Column where you would like the extra data to go and go to the Worksheet menus and choose Insert Column Go to the Worksheet menus and make sure that View:Database Headers is checked. Click in the database header row cell for the column you want to class in and type in a formula of "=C" then hit Return That should give you the class of each object in a subrow of the database.

Everything other than OpenGL rendering in VW2017 is CPU based, so there is not a lot you can do to speed up renderings. Much of the code is still single threaded. I am not certain about Hidden Line Rendering.

Can't do it the way you are trying. Database subrows can't be individually referenced between worksheets. Since the data in worksheets is dynamic, it would give you a LOT of room for future problems. In your example, what would happen if someone changed the sort order of the first worksheet? Cell C5.1 would now have different data than you want. How many different types of trees do you usually have in a project? If it is a "reasonable" amount, you could probably do a manual tree schedule and pull from there. Or maybe you just need to manually edit the proposed conditions worksheet. You could use something like =count((S='Your Symbol Name')) or =count(('Plant'.'latin name'='Your plant name')) to get the quantities. I think if you copied and pasted the names from the database into Column A, your could even use a formula like =count(('Plant'.'latin name'=A3))

I finally found the thread with the other Revision Block problem. Turns out that a lot of the problem was the the :r Fields were included in a Group, not just as text in the drawing. I hope this helps.

Yes, VW12017 still has the Log Time In Program preference. What operating system and printer driver are you running?

I thought that someone else was having a problem with their revision data late last year or earlier this year. I vaguely remember hunting it down and concluding it was a bug, but now I can't find the thread or my notes.

I don't think there is a way to have it update automatically. As far as I know Worksheet must be manually recalculated in order to show the most current data. I have not tested, but an old post I was looking for seemed to indicate that calling Recalculate from one worksheet actually recalculates all the worksheets.

Yes, I get the same thing in 2017. You should report it as a bug. Printing directly from a worksheet should always print in color regardless of what the Layer Colors option is. Right now it is printing in Black and white even if there is not an image on the drawing and regardless of what colors the layers are set to.

I am 99.9% certain that 2016 will print worksheets in color. I am 100% certain that 2017 will print worksheets in color. I just printed both from the worksheet file menu and from a worksheet image placed on a design layer and was able to get 4 different colors (Red, Blue, Green, Black) text to print from a worksheet. Where are you printing from? Design Layer, Sheet Layer or Worksheet? If it is a layer is the image in a viewport? Do you have the Advanced Properties setting for the Viewport (bottom of OIP) set to BW only? Do you have a viewport Override on that is set to Black for the class the text is in?

Try the following script. Write back if you need more information. Procedure ChangeAllWindows; {©2017, Patrick Stanford, pat@coviana.com Licensed under the LGPL} {No Warranty Expressed or Implied. Test thoroughly before using on production data} {Make a backup copy before running} {Turns off the Louvers on Sash setting for all windows in the file.} {Do no operate heavy machinery while using. May cause drowsiness} Procedure ChangeWindow(Hd:Handle); {This could be changed to any other Window parameter by changing} {the Field Name (third parameter) to the correct value and } {changing the last parameter to the new value to set} Begin SetRField(Hd, 'Window','LouversOnSash','False'); ResetObject(Hd); End; Begin ForEachObject(ChangeWindow, ((R IN ['Window']))); {runs the ChangeWindow procedure for every object with a Window Record} End; Run(ChangeAllWindows); Procedure ChangeAllWindows; {©2017, Patrick Stanford, pat@coviana.com Licensed under the LGPL} {No Warranty Expressed or Implied. Test thoroughly before using on production data} {Make a backup copy before running} {Turns off the Louvers on Sash setting for all windows in the file.} {Do no operate heavy machinery while using. May cause drowsiness} Procedure ChangeWindow(Hd:Handle); {This could be changed to any other Window parameter by changing} {the Field Name (third parameter) to the correct value and } {changing the last parameter to the new value to set} Begin SetRField(Hd, 'Window','LouversOnSash','False'); ResetObject(Hd); End; Begin ForEachObject(ChangeWindow, ((R IN ['Window']))); {runs the ChangeWindow procedure for every object with a Window Record} End; Run(ChangeAllWindows);

Just realized this was not supposed to be a discussion thread. Also, I did not read the above posts carefully enough and my comments do not directly apply to the other posts above. My apologies.