Viewports need class defaults...one way or another

[grant_PD]

Viewports end up in classes, there's no two ways about it. Why there is not a viewport class that is automatically assigned is beyond me. But, if I can't have that, then can I have:

A class assigment drop down when I create a viewport. This makes sense, since I can pick and choose which classes and layers are IN the viewport, and I can choose which layer the viewport goes IN.

A class assignment that is editable via the navigation palette.

As a broader note, I feel that anything PIO should have the ability to have it's class predertermined. Drawing labels, sheet borders, callouts, etc.

[Dieter @ DWorks]

As a broader note, I feel that anything PIO should have the ability to have it's class predertermined. Drawing labels, sheet borders, callouts, etc.

They can through the VS editor. But I do want some way to define the default class for all objects, even those you can't set through the VS editor, and let is be a lot easier than that VS editor.

[Kevin McAllister]

I don't think Callouts can have their class defined by the VS Editor... KM

[grant_PD]

I don't think it's nice for a software company to throw an antiquated scripting module at their consumers and essentially say "you figure it out." I'm not a coder, I'm a designer. I don't have an IT department to write custom codes for me. I have a lot of other things to be doing instead of making sure that my drawing labels aren't in some other class than a drawing label class.

axiom: Everything in VW exists ON a layer and IN a class.

If that's the case then why can't we have defaults for specific things?

How come we can't have a scripting module like Adobe's actions palette for Photoshop?