Pat Stanford

Detail will require operating system information, but you should be able to make an Alias/Shortcut to the location you move the library to on the HD in the place the library was on the SSD. If I was doing this on a Mac, I would probably use a SymLink.

You are reading it right, I just think the documentation is wrong.

IsPolyClosed dates back to at least 2012. I think it is much older than that. There was a post to the Vectorscript List in January 2013 that included this.

Have you upgraded to SP3? If not try that and let us know if things are better.

Unfortunately, the 2-way worksheet only works on Record.Field data. Anything (actually I am not positive it is anything, but almost anything) that you use a "default" formula for (=L, =C, =T, =Length, =XCenter, etc.) can not be changed in the worksheet database. Now, if this is functionality that you really desperately need, it MIGHT be possible to use a scripted Worksheet Function. Or to add a custom Record.Field that you could change in the worksheet coupled with a script that would then write that data to the object. But both options are likely to be painful and less than satisfying. Sorry.

Since you have both versions installed, can you try two things: 1. Create a file in VW2015 add a text block and type some text and some ALT-codes. Save the file and open in VW2017. Does the text look the same. 2. Check your Font Substitutions. Go to VW Preferences, Display tab, and click on the Edit Font Mapping button. Do this in both versions of VW. Is the font you are using (or think you are using) mapped to something else in one of the versions?

One thing to be careful of is that Vectorworks only understands a few types of units. It understands length and area (and maybe volume and angle). So if you have fields that are defined as Dimension, you can do things like 1' +1" -2cm + 25.4 mm and come up with the correct answer. For units that VW does not understand you have to define them as Numbers and store them without any units attached. If you create a field to store a weight, you have to enter it as 57, not 57# or 57 kg. When the next person comes along and uses a different unit, your calculations are going to get screwy really quickly. There was a $50M satellite that was lost on Mars due to different groups using different units. In a worksheet where you know you have control of the base unit, you should be able to do a conversion to a single known other unit without too much trouble. Note that some of the PIOs (specifically the Space Object, maybe others) try to get around this by defining two fields for things like Area. One will be a number the other will be a text field and will contain both the digits and the unit marks. You have to make sure to choose the right field if you need to do math(s).

The class and layer information is built in to everything. Formula for Class i =C For Layer is =L

'Window'.'RoughOpenWIdth' 'Window'.'RoughOpenHeight' 'Door'.'ROWidth' 'Door'.'ROHeight'

With the worksheet open for editing, go the the Worksheet View Menu and uncheck Database Headers. All data in a database MUST be either object specific calculations (things like position, area, perimeter) or Record.Field data. The Record.Field data can either be PIO Parameter Records (i.e. Door.Width) or user generated records (MyRecord.MyNoteField). So to put in notes, you can create a user Record and attach it to the objects that will show up in the database. If you create a Note field (whatever name you want), you can then put a formula of =MyRecord.MyField into the database header to display the data. Since record.field data is 2 way, what you type into the worksheet will be stored in the record attached to the object. If you edit the field from the Data tab of the OIP the changes will show in the database when it is recalculated. I don't understand the third question, but I think the answer is no. All formulas must go in the database header row and apply to every object in the database. Of course an object that does not have MyRecord attached will not show anything in the cells referencing that data. Ask more if you still have questions.

Try the field accessed from 'Window'.'OperableSashLen' You might be able to use this to generate information about the maximum open area of the window. I can see where it would be useful, but VW does not support it automatically right now.

VW will support OBDC connections to external databases. What database are you using outside of VW? Does it also support ODBC? If not, you will either have to program your own solution (not recommended), switch to a database that does support OBDC (recommended) or accept that you can't use a single database both inside and outside VW.

What is Vent Area and how accurate do you need your callouts to be? Would this be considered Screen (as in insect screening) area? Could you use the net area of the door or window as a surrogate?

If you really want a script it is doable, but if you go to the far right end of the Mode Bar, there is a disclosure triangle. Click that and you will get a list of all the preference toggles that are available. Turn on the Join Walls and you will get an icon in the Mode bar that you can click to turn on and off Join Walls mode. Lots of other good prefs there also.

VW should handle it better and do what you want. There is lots of mumbo jumbo I could throw at you about color spaces and 8 vs 16 bit color, but none of that matters. VW should be able to pick a color and directly reproduce it. I think the render is using "more" colors than 2D in VW can use. What happens if you render in OpenGL and try the color picker thing? Or change the color slightly and do the color picker thing in FQRW?

Both the Door and Window object contain User Field 1 thru User Field 10, but these are TEXT type fields. You could put your Vent Area in those fields, but you will need to convert the values to numbers so you can add them up. The proper syntax to access the field is 'Door'.'UserFld1' thru 'Window'.'UserFld10' A small custom worksheet script (basically a custom worksheet function) could be written that would take the text value and convert it into a number that you could then work with. Door do have a Net Glazed Area. This calculates when you turn on Use Vision Panels in the Leaf pane. It can be accessed in a worksheet at ='Door'.'NGA2'

Except for the fact that I can't figure out how to make a dimension that does not use the dimension line, so my second option is out. Maybe you need a custom PIO to do your dimensions rather than the standard dimension tool. Not soon, but maybe soonish? If you don't hear back from me in a week or so, please ping me and remind me.

My Python is not very good and I don't have time to figure it out tonight, but here is a Vectorscript that is close to what you test script does. You are going to have trouble with your script because the Message command is broken in 2015-2017 and does not work during the execution of a script. It will display the last message after the script completes. This script should been every time you cross over the edge of a rectangle. If you hover just right, you can get it to repeated beep. When you click it should quit. Hopefully this gets you somewhat closer to what you want. Procedure TrackObjectTest; Var H2: Handle; X1,Y1, Z1: Real; Function CheckObjCallback(Hd1:Handle; X1,Y1:Real):Boolean; Begin If GetType(Hd1) =3 then SysBeep; End; Begin While Not Mousedown(X1,Y1) do TrackObject(CheckObjCallback, H2, X1,Y1, Z1); End; Run(TrackObjectTest); To do your action or not, just add code into the CheckObj procedure. If Hd1=Nil then set flag to tell the main program to exit the loop. I know I am not being very clear. Maybe tomorrow I can do better.

In my opinion, Marionette is great for creating objects, but not especially good for modifying objects that already exist, especially manually drawn objects. Yes a script (Vectorscript, Python, probably Marionette) could be written that would scale objects from the center (or simulate it by scaling and then moving the object), but you would probably need a lot of script to handle all of the things that true parametric constraints would give you.

Not what you want to hear, but the easiest solution would be to change the dimension style so the numbers are above or below the line rather than in the middle and then use None fill. Anything else you are probably going to have an ongoing fight with. Next simpler option would be to use a dimension standard with no line at all and draw in the lines. If I was to do this, I would probably do a polyline with 3 segments and then use the Reshape tool to turn off the visibility of the middle section. That way you only have 1 object to move with the dimension, not 2.

It is not part of the Profile, but rather part of the Settings. Go to pull down with your user name at the top left. Choose Account Settings. From the dialog box that opens choose Signature.

Normally when things in Vectorworks "disappear" it is because the layer and/or class visibilities are not set properly. In the Navigation Palette, check that the Class Options is set to Show/Snap/Modify Others, and that all of the classes are set to Visible. Also check that the Layer Options are set to at least Show/Snap others and that the layers are all set to visible. Once you get everything back to visible you can then start thinking about how you want to use your visibilities and start turning things you don't need back off.

Yep it is out and available for download. I got the press release earlier. I am sure the announcement on the forums is coming, just a little behind. http://www.vectorworks.net/support/downloads/product-updates or check for updates from the Vectorworks menu.

I believe that TrackObject is designed so it will work without requiring an event enabled object, so I can be used as just part of a normal script. If you need the functionality of an event enabled object it probably would be in the MouseMove event, but I am not positive.

Check the release notes for VW2017 SP3 released today. It has a fix for this.