Pat Stanford

Often this has to do with drawing & redrawing handles. Try Grouping the object, change the layer of the group and then switch layers and Ungroup. I would guess this will be much faster.

Yes, Hans-Olav is correct. It is also pretty well described in the VW Help. Search for Advanced Section Viewport Properties an excerpt:

The fixed "insertion point" idea should not effect the actual image of the worksheet at all, only where it is placed on the page. If it does otherwise it is a bad design decision.

@MTRobinCould a different way to describe this request be: Pick the "insertion point" of worksheet images on drawing. If the Top/Left corner is picked as the insertion point and the worksheet increases in size, it will expand to the bottom and right. Similarly, if the Bottom/Right corner is the fixed point and the size of the worksheet expands, it will grow to the top and left. This option will allow worksheet images to be places at the edges of drawings and automatically expand into the drawing area instead of always expanding down and requiring the image to be moved to be on the page. The 9 point selector in the OIP as is used to determine the fixed point of 2D object (polygons, rectangle, circles) could be used to locate the fixed point.

@nahekul Thanks for continuing to check that out. And thanks to the development team at Vectorworks for making the changes necessary to have Space objects return the data expected.

I am not certain that you can store a Workspace in the Workgroup folder. I know it works in the Application folder and if you edit one of the standard workspaces it saves it in the User folder. OK, I just checked and yes you can store the Workspace in the Workgroup Folder. You need to have a folder at the top level of the workgroup named Workspaces and you store the workspace files (*.vww) in that folder. But be careful, I think that data like the current active tool and the tool preferences are stored in the workspace file. If you have multiple people using the same workspace out of the workgroup, the last one to quit at the end of the day will overwrite any previous saves. Your tools may have different settings when you open VW the next time.

@Gadzooks, Thanks for the kudos, but my reading of the question is that @DCarpenter wants to do the opposite. He has the objects in the worksheet and wants to list the Location names. I don't think there is an easy way to do this. The LOC is not a property of the object. When you use the LOC criteria is goes through and compares every object to the objected named in the LOC and only returns the ones that do. If you have a "reasonable" number of LOCs (say 10-20 max) that don't change very often I would probably just create a separate database for each LOC and use that as a work around. If you have a large number of LOCs or they change name frequently (like you need to do this for every project), then we have to go to much harder options. The best option I can think of right now, which will probably be deadly slow on a large drawing) would be to create a custom worksheet function that will take an object, compare it to every object in the drawing with a name and return the Name of the first object that has the object in that LOC. If you can accept the LOC object being in some what identified (always in the same class, having a custom record attached, being on a different layer) then that would greatly decrease the number of comparisons and speed up the operation. Also, the way your database is set up, it is not going to work as you expect. Since you have your upbeats SUMarized, if you end up with objects in different LOCs, it will return a cell with a dash ("-") (I think) because the data is not identical for every object. Let me know if you need more help.

It does not matter what the file is named. The only thing that matters is that it is stored in the correct folder inside Defaults, Inside Libraries, Inside a folder that is defined as a Workgroup Folder. If you have a single file with multiple different object types, they won't show up unless that file (or hopefully an alias) is in the correct folder for each of the object types that you want to be Default Content.

If you want it to show as Default Content (say Line Styles), then you have to have them in EXACTLY the right location. Go to your user folder and copy the Libraries/Defaults complete folder structure to your Workgroup Folder. Libraries needs to be at the top level of the Workgroup folder and the rest of the hierarchy in enclosed in that. Then put the file(s) with the line styles you want to be Default Content into the Attributes - LineTypes folder. If you don't want to have to break them out to separate files, I think you can just use an alias to the file so you can use the same file in multiple locations. I can never remember is you need to restart VW after you change the Workgroup folder structure or not. If you put the file there and the LineStyles don't show up, try restarting.

Objects are on a different layer and the Layer Options are set to Grey Others or Grey/Snap Others?

Have you met the Chance Brothers? Slim and No? Just kidding, but what you are asking is not easy in VW, but it is possible. The only place in VW where you can be guaranteed to have a unique value is in the NAME field in the OIP. You could store your GUID there, but that is also used by some users and in some objects for other uses. Also, it is use accessible, so there is no way to keep someone from changing the value and messing up your database. You best option is probably to create a hidden record format and use that to store a UUID. In Vectorscript, there is a CreateUUID function, so it is probably in the SDK also. Basically, your script would first check for an instance of the hidden record. If it is not there, it would attach the record, create the UUID, and store the UUID into the record. Then that UUID could be stored into your database. Come time to go backwards, you would have to look for an object with a record.field value equal to the UUID in the database. What you do when you don't find and object depends on your needs. You might want to reach out to @John McKernonand see if he can offer any advise. His LightWright lighting paperwork program handles back and forth between VW and Lightweight robustly. That seems similar to what you are talking about.

There is a "bug" in the MESSAGE() procedure (or a bad design choice) that causes the Message to only display at the end of script execution. Probably not really useful for what it sounds like you are doing, but for debugging purposes, I use AlrtDialog. You have to hit return after each occurrence, but at least with a CONCAT you can display a string for trouble shooting purposes.

The biggest advantage is that items in proper locations in the Workgroup/Project/User folders will show up as Default Content in the various tools. Favorites are great if you are just using symbols, but if you want things to show up natively, especially across different object (PIO) types, then W/P/U folders are better.

And maybe this one also.

Check out these two posts for a stating point and then ask again if you need more information.