Pat Stanford

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.

Zoomer and I have been through this before. Please try to remember that the way you use VW is very different (no matter who you are and how you use VW) than the majority of users. The idea of Screen Plane and Top/Plan is absolutely critical to many of the primary industries that VW excels in. Specifically entertainment lighting. If the idea of hybrid symbols goes away, (hybrid symbol automatically separate out Screen Plane objects from other objects), then nearly all of the benefits to that industry go away also. Any time you are advocating to take away some capability because it does not make sense to you, please really consider how others may be using it. The above being said, if the separation is truly hindering your workflow, it is reasonable to try to ask for changes to keep functions you don't use out of your way. It is not reasonable to ask for things to be removed that are heavily used by others just because you don't need, don't like, or don't understand them. My 2¢. To be repeated as necessary when the idea of removing key capabilities arises. ;-)

What do you want the door and window to look like? There are Vectorscript commands that will let you interactively click on two points (even with a rubber banding preview). That will get the points. Then we just need to figure out how best to draw the stuff between. Could be Marionette. Could be just a group created via the script. Do these doors/windows need to be able to insert into VW Wall objects?

C='GetDist' is objects that are in the class named 'GetDist' C= Class Name L= Layer Name

The options you have been provided should keep the view from switching to Perspective the NEXT time you switch from Top/Plan to a 3D view. If you are already in a Perspective view, you can change it from the View menu, Projection options or from the Projection pull down in the View Bar. If you have Saved Views, you will have to recreate them. I can't find a way to edit the Projection setting in an already existing Saved View. Just enable the view, change the Projection and Save it again with the same name saying yes to Replacing.

What are you going to do with the data? Do you just need to know what the distance is (One time display?) or need to place that distance in the drawing somehow? If you just want a "dialog box" to come up and show you the distance then a script will be a better and easier option. In my opinion, Marionette is the best option for programmatically creating objects in a drawing. Traditional scripts are a better option in most cases for modifying objects that already exist. Examples would be changing classes, fonts, colors, turning on options (Like Multiple Labels in Space objects) and even changing text blocks (company name changes) The following script will display a dialog box showing the distance between the first two selected locus points in a file. It does not check that the selected points are loci and will error if run with other type objects selected. If you need a more robust version it would not take much to check the object types and fail gracefully. Procedure LocLocDistance; Var H1,H2:Handle; X1,Y1,X2,Y2,Dist:Real; Begin H1:=FSActLayer; H2:=NextSObj(H1); GetLocPt(H1,X1,Y1); GetLocPt(H2,X2,Y2); Dist:=Distance(X1,Y1,X2,Y2); AlrtDialog(Concat('Distance is: ',Dist)); End; Run(LocLocDistance);