Pat Stanford

Or as I suggested, don't try and make the cut list from the model, but rather put duplicates of the parts on a different layers so that Length/Width/Height to work. You could still get the count by counting the total number of each part and subtracting one for the the one on the "sample" layer. It will work better if they are all symbols.

I think we need a better understanding of what you are trying to do. If this is for a PIO you are writing, then displaying things in the OIP is as easy as defining them as Parameters. If this is for a PIO you do not have access to the code for, then about the only option would be to attach a Custom Record Format and write you calculated data to a field and then view that in the Data pane of the OIP. I don't think there is a way to get anything to display in the Shape pane of the OIP for a PIO you don't have access to the code.

Have you tried PROCEDURE SetTopVisibleWS ( worksheet:HANDLE ) ; ?? You may have to also PROCEDURE SetWSCurrentCell( worksheet:HANDLE; currentCellRow:INTEGER; currentCellColumn:INTEGER) ;

If you find something that works, let us know what it is.

Bruce, I know you have asked similar questions before. The answer has not changed. VW Worksheets do not have the ability do to what you want and what your brain can do. The only work around I can think of is to make symbols of the parts and then put the symbols onto a "detail layer" so they all match up with the cardinal length/width/height functions and then report on the dimensions from there. Sorry.

It depends on how you have your title block configured. As you say, Project data is changes in one place for every title block in the file while Sheet data is changed on a sheet by sheet basis. There are Date fields in both because some people want all drawings to use the same date and some people (like you) want the data to be editable on a sheet by sheet basis. Edit your Title Block Style and then the Title Block Layout. Select the block of text that represents the date. At the bottom of the Object Info Palette change the linked field to the Sheet Data field you want to use instead of the Project Data it is currently linked to.

Not an easy one because the link is really one way, Is an object in a Loc. There is no easy way to find out What Loc is an object in. The is no dynamic way to get that information. It is fairly easy to write a script that would go through and store the Loc name into a Custom Record (or a spare field in your device record), but if you moved a device to a different Loc and did not rerun the script the data would be out of date. Actually let me think about that more. It MIGHT be possible to create a worksheet script so the script would run every time the worksheet is recalculated so it would be more dynamic. But depending on the number of devices, it could be quite slow. Here is a link to the thread the last time this question was asked.

I don't believe there is any guarantee. I think that it is in the order that the polygon was drawn. So if you always draw clockwise then the returns should always be clockwise.

Yes. Just make sure the check box for Including Components of Symbols is checked in the database criteria.

You have the Render mode set to Sketch. Set it to Wireframe (View menu:Rendering:Wireframe) and all will be well.

It depends on the size of your site. The larger the site the larger you want the display grid at. When you zoom too far out that the grid becomes very close together, then VW stops displaying it as it will just show as blue. I would bet for Landmark something like 5 feet or 10 feet for the display grid would probably be in the right range. But zoom to full size on your monitor and see what makes sense based on your plot size. 1" for the Snap grid might also be to small to be useful in landscape. Do you really need everything to be accurate to the nearest inch?

The article on list browsers from Vectorlab has been reworked and uploaded by the author ( @_c_ ) to the devloper pages. https://developer.vectorworks.net/index.php/User:CBM-c-/VS-List_Browsers_part_1

That is my understanding also. For Default Content if you have the same file name in the Applications folder, the Workgroup Folder, and the User Folder, the one in the User folder will be used and you will not see items that are in the files in the Applications folder or Workgroup Folder. And similarly, a file in the Workgroup Folder will hide objects in the Applications Folder. As Christiaan says, it may or may not be desired based on your needs. You can still manually navigate to those files to access the data if needed. Setting up to hide default content is a little like bringing a custom workspace forward when you upgrade versions. It will still work but you won't get any of the new features until you do some work. For things like Text Styles you probably don't want or care about the default content and only want to use your own versions. For something more complicated (maybe Doors or Windows), you probably at least will want to take a look at the factory Default content and see if any of it is useful on the next major upgrade.

Peter is correct. The following compiles and toggles between Show Others and Grey/Snap Others. PROCEDURE LayerOptionToggle; VAR LayerOption:INTEGER; BEGIN LayerOption:=GetPrefint(506); IF (LayerOption = 3) THEN SetPrefint(506, 6) ELSE SetPrefint(506, 3); END; RUN(LayerOptionToggle); The line before an Else does not need (indeed can not have) a semicolon at the end. Most other lines must have a semicolon at the end. Even though it is a little more typing, I would probably have written it like this: PROCEDURE LayerOptionToggle; VAR LayerOption:INTEGER; BEGIN LayerOption:=GetPrefint(506); IF (LayerOption = 3) THEN Begin SetPrefint(506, 6); End ELSE Begin SetPrefint(506, 3); End; END; RUN(LayerOptionToggle); That way the lines between the Begin/End pairs alway can have the semicolon and the only one that does not have it is the End right before the Else.

DoMenuTextByName('Wireframe Render Chunk', 1); I already had it pasted in when Julian's reply came through, so I will just second it. All of the "Chunk" names are shown in Appendix H of the Vectorscript Appendix.

Or just hold down command and type the hyphen/minus key. It should make all the fonts smaller. Command and the =/+ key does the opposite and make everything bigger.

Does it come in all files or just new blank files. Have you tried to use a template file and see if they show up?

It is likely that Apple made changes in OS11 that broke the functionality and Logitech has not caught up yet.

That mark indicates that the Section Marker is not linked to a Viewport. Unfortunately, there is no way to turn it off. Yet. I don't think that the mark exports to PDF or Prints.

I don't believe it is possible directly. Worksheets are only able to see objects that are present in the file (from a programming standpoint, objects that have handles in the drawing space). You might be able to apply the textures to objects on an extra layer and then get the information, but I have not tried it.

@markiflamer Nope, as far as I know, there is still no way to do relative references in a Worksheet Script.

The Workspace Editor is located (in the US version) in the Tools menu under Workspaces. I you just choose to Edit Current Workspace and you are using one of the default workspaces the edited copy will be stored in you user folder. While I stick to the stock workspaces because it makes helping people and troubleshooting easier, we just did yesterdays Los Angleses users group meeting on customizing VW. I see a few more reasons for a custom workspace than Peter mentioned. The two biggest are to add things that you use on a regular basis to the Right Click menus, or to create a custom palette to use with the "Smart Options Display" (heads up menus in VW2021). We had a relatively large argument about if you should and how much you should modify from the standard workspaces, and I was one of the people most advocating keeping close to stock. But in the long run, set VW up so that it makes sense to you. If you have another program that uses L as the shortcut for line and you find yourself trying to use that in VW, then make the change. You can always switch back to stock if you decide you don't like it. Or change it again until you get something that is comfortable for you. In the Workspace Editor you have different panes you can select at the top for Menus, Tools, and Keys. For Menu's and Tools, all of the options are in the left hand pane. In the right hand pane you have the Menus and Palettes. Select the tool you want in the left pane and drag that to the place you want it in the right pane. If you "indent" when dragging the menu/tool, it will be placed as a "sub" option. To add keyboard shortcuts, select the tool/menu in the right hand pane and then pick the modifier keys you want to use at the bottom and then type the character you want to use. If that combination is already in use you will get a warning. I hope this is enough to get you started.

A Saved View is simply a script that set the view, layers, classes, and rendering mode. It is not a state of the drawing. The best you could possibly get would be something to tell you the last Saved View that was run, but there would be no way (without major changes to what Saved Views are) to tell that you can run a Saved View but after running it made other changes. So you call a view that sets a Left Isometric view and then you manually change the view to Right Isometric. But the last view you ran was Left, so that is what is displaying as the view, but it is not the correct view, so what would you want to have happen in that case? Without completely re-architecting what Saved Views are to prevent the user from changing the settings, then having a display of the non-existent "Current Saved View" will create a situation where the program is lying to you much of the time.

This thread has most of the posted experience with M1 and VW.

Class visibilities in Viewports can be adjusted by selecting multiple Viewports in the Organization Dialog Box and clicking the Edit button. Unfortunately, Class Overrides are not editable there.