line-weight

By this do you mean a copy & paste of the camera itself, from one viewport to the other?

I have a workaround method to sort-of get a hole right through (and keep it as a site model object) - I think mentioned in one of those other threads.

Unfortunately the rotation is rather crucial! I don't think adding RW cameras to viewports helps in this issue. If it were the case that I could define a single RW camera and then tell multiple viewports to use it, then the problem would be solved, but for some reason (and anti intuitively) that's not how cameras work in VW.

A version of that script that would let the user select the source viewport, then bulk select a number of destination viewports, would be a rather handy thing! One of the most annoying things about having to duplicate or copy-paste viewports in order to replicate a viewpoint is that it constantly messes up any attempt at having viewports named in an organised way. A typical use case: I have an "existing" and "proposed" version of a design. Maybe I have "proposed" options A, B and C, with different versions created by layer or class, and then selectively shown or hidden. All four viewports want to be looking from the same viewpoint, for a fair comparison. But if I want to change the viewpoint of all of them, I have to re-duplicate them all, rather than just changing it in one, and copying to the others.

Thanks, that's interesting to see - would it still work if drawing 2 had no camera attached to it? (edit) To answer my own question, yes still seems to work if I delete the camera.

If it was scriptable then you might think the eyedropper tool could do it ... but it can't unfortunately. At the moment what I end up doing is duplicating the viewport whose viewpoint I want to replicate, then using other means (such as the eyedropper tool) to transfer other properties to it (eg class and layer visibilities and so on). It's a messy way of doing it though. I've long thought it's a strangely missing functionality from VW. Unless it's me that's missing something.

If I have 10 sheet layer viewports, all of which are rendered views taken from the same specific viewpoint, there is no way I can set things up so that I edit that viewpoint and it replicates across all viewports - is that right? I don't think a "camera" can link to more than one viewport, and I don't think there's any way to define the viewpoint in a viewport style. ....or is there anything I'm missing?

It's nowhere near as easy as it should be! You might want to have a look at a couple of recent threads on a similar theme: One problem is that the relevant tools are a bit of a nightmare to use. The other issue is that if you want to cut the "ground" around foundations & footings that spread out as they go downwards.... you basically can't.

(This request may well have been made by others already. Ignore if so.) I can tell a saved view to "restore data vis", ie. make certain DVs active when I activate that Saved View. However, I can't directly tell it which DVs - as far as I can see, I have to activate the saved view, turn on my DVs, and then "redefine" the Saved View making sure the "restore data vis" box is ticked. Similarly, what DVs are associated with what Saved Views isn't shown in the Organisation dialogue, as far as I can make out.

Thanks once again! This appears to work fine. Rounding is not a problem - because any numbers I give it will have no more than 4 decimal places. Thanks for your help. This will save me a lot of time in the long run.

So: I have confirmed this is what happened: my HD had about 40GB free when I started a session in Vectorworks. The amount of swap memory used gradually goes up and up - it's got to about 36GB and this means that in combination with other applications (using about 2GB) there is less than 2GB left on the HD and Vectorworks tells me there's not enough space on disk to save the file I'm working on (I have to go and delete a couple of backups to make it work). Is that what's supposed to happen? Shouldn't VW know when it's nearly used all of the space on disk, and stop adding swap files at some point (or remove old ones)? Does this count as a "memory leak" or does VW make some assumption about the amount of space it can use on my HD for swap files, some amount that is higher than what I commonly have available?

I've realised that I think I want ConDateNum and DemDateNum fields to be a number with 4 decimal places, eg. 1870.0322 or 2025.0407. I've tried fiddling with various things in the script (the bits that look like they specify whether those fields are integers or numbers, and how many decimal places they have) but without success...can you point me in the right direction @Pat Stanford?

*bump* Any GIS experts out there able to answer this?

I can confirm, this works - thanks. Agreed that a better solution might be to rename the classes so they don't contain asterisks.

Thanks again! This worked perfectly again. It successfully acted only on classes with names beginning "**buildings". I realised that actually I might want to run it on all classes beginning with "**". So I swapped "**buildings*" for "***" but as I expected might happen, this resulted in all classes being selected, presumably because it simply reads it as three wildcards. Is there an easy way around this? I tried various things like ForEachObject(Execute, ((C='**buildings*' OR C='**roads*'))); without success.