Isn’t it about time we had both layer import and design layer viewport in the same file?

[shorter]

Current behaviour…

 

you can reference using layer import

 

or

 

you can reference using design layer viewport

 

while you can create a design layer viewport from a referenced layer you cannot create a ‘referenced’ design layer viewport at the same time as using layer import referencing

 

both methods have been around since 2009?

 

both have been independent

 

isn’t it about time the two co-existed?

 

then we can do what Revit and autoCAD do

 

Edited February 7, 2023 by shorter

[Christiaan]

It is about time.

 

What I've found is that I want to use Layer Import for referencing my own files into each other (because this provides better control of Class and Layer visibilities and overrides) but I want to use Design Layer Viewport for referencing third party files because I don't want to contaminate my file with their classes/resources and I want to be able create viewports that I can move into the correct position relative to my model.

 

Layer Import should never have been called 'old' or 'legacy' as it once was. They're both useful for different things.

[shorter]

Use filters, @Christiaan use filters…

[Christiaan]

Okay, the bit about contamination can be removed, thanks 🙂

[Andy Broomell]

42 minutes ago, shorter said:

Use filters, @Christiaan use filters…

 

How can you use filters when the other person's class and layer names are sorts of a mess? I could see filtering out their classes and layers if they all used a common prefix, but that's pretty rare.

[shorter]

That’s what the ‘add prefix’ option is for when you import a DWG.