I have seen latest view nodes on daily build. They work like a charm. But I have a question about View Extents node. Crop Extents output returns a domain. If Crop Extents means the crop region, I would rather have it as a curve or at least a curve alternative. Because Crop Region is not always rectangular.
Sorry for bothering you… but can we get also the exact opposite of that Python component?
I got a bunch of flats with crop regions set manually in Revit and I need to receive boundary curves.
I ended up using a slight variation on this for a workflow where I need to export Revit elevation views individually for an interior designer, who then xrefs them into AutoCAD model space for further design work.
The crop region is still defined manually in Revit (more an art than a science), but Gh reads the crop boundary, creates a framed masking region from it, and then offsets the crop region outward so the boundary remains visible in the DWG export while still clipping everything outside the view. The result is a clean export with a selectable crop boundary in CAD.
Definitely a pretty niche workflow, but sharing in case anyone else runs into the same issue. Thanks to everyone who contributed to this thread—