SamIWas

Sigh...that's what happens when I don't finish reading the entire post and move on to the responses....🤔

Note that the eyedropper tool works on viewports with layer and class settings and is pretty immediate.

So THAT'S why so many of my scripts don't report what they used to.

Yeah...I've done the deal with PDFs for many years, ungrouping then dealing with the resultant parts. For some reason, I just missed that they were there since they were hidden and weren't selecting.

I just opened this back up to say that I found the issue. The lines were there, but were covered with a white rectangle, thus not appearing when I showed everything. I was sure I had deleted them, but apparently I had not.

I had imported a pdf, which I ungrouped to get normal lines. It brought in hundreds of thousands of lines, which of course bogged down the machine. I deleted all of it. Weeks later, I'm working on the drawing, and periodically when zooming or performing a move command, these phantom lines reappear for a few seconds before going away. Being that it's 100,000 of them, it causes a long pause on my MacBook Pro. I have turned on every class and layer, and the lines are not actually in the drawing. They are just phantoms showing up randomly. Any idea how to get rid of these...it's absolutely draining my workflow speed. I'm starting to think I will have to manually copy each and every existing thing to a new document...

Holy crap, man...that worked! This is going to make updating old files, and inserting new doors and windows, so much faster!

Thanks Pat! I'll try this tomorrow and see how it goes.

Holy schniekies. So, it looks like selecting a bunch of doors throughout a document and trying to change records in this way wouldn't work very well. What I was trying to do was create a script that would assign my default class scheme to doors that I pull in from older drawings.

The test script is set to give me an alert box with the handle. If I put the door alone in the drawing, it returns a series of numbers. When I put the door in the wall, and select only the door, I get a blank.

With the lighting device, I can just use SetRField and GetRField to get and set info for the lighting device. With door, this doesn't seem to work. As a test, I used GetRField(h,'Door','2DLeafClass') and GetRField(h,'Door','2D Leaf Class'). but neither works. Is there different way to get and set door info via script? EDIT: I have found that it works when the door is not in a wall. But, once the door is placed in a wall, I can no longer get the script to pull info from it. Surely there is a way.

Yeah, I already do that via text files. It's just an extra step in the process. I know that a direct, immediate, and automatically updating connection is possible with Filemaker via ODBC. I've gotten it working briefly on small projects, but it is mind bogglingly difficult. I'm hoping for VW and FM to work together to make a solution with easy, automatic connection between the two. FM Is so powerful when it comes to tracking and reporting data.

I just want FileMaker connection. I don’t even have excel.

Dear god, please make this work with FileMaker. That would be worth the cost of the program alone for me. Well, maybe worth $1000. please please please

Are you saying you have a spreadsheet outside of Vectorworks and want to import that spreadsheet, match each line to a symbol, and apply the data from that spreadsheet to the symbols, filling the necessary record format(s)? If so, yes. I have dozens of scripts which do this. Each symbol/lighting device/plug-in has a unique ID, and the script matches the data from each line to the symbol using that. It's can get quite complicated. The basics are to use OPEN(filename) and then create a loop to read each line and separate each cell into a variable. Find any symbol which matches the key variable, and SETRFIELD to apply the variables to the records fields.