View Sets reset to all on when I delete layers

[Anonymous]

I have to rebuild all my view set layering when I delete layers. I'm not deleting any layers that are part of the view sets, just extra layers that come in when I drop in a module. Why is this the case? Is there a setting somewhere that can prevent this?
Thanks.

[Link]

This doesn't sound right to me. Once a layer combination is assigned to a view, it is mapped permanently. Modifying the layers within the combination should have no effect on the view. Deleting/renaming that layer combination will however affect it!

Maybe you can better describe what you are doing, and even include a screenshot on machine/software specs.

Cheers,
Link.

[Karl Ottenstein]

I sounds like your views were memorized with "Custom" rather than with a named Layer Combination perhaps?

Karl

[Anonymous]

I use view sets only to define layer combinations. I never toggle between layer combinations in layer dialogue, I don't even have any saved layer combinations. The problem happens like this. I insert a module that has a bunch of layers in it that I don't use, then I redefine the individual items onto layers that I do use before deleting the new, unused, extra layers. After I delete unused layers all of my view sets get redefined with all the layers on. The view is the saved, the display options is saved but the layers all turn on. I've reinacted it 4 times.
Any more help?

[Karl Ottenstein]

DHURD wrote:
I don't even have any saved layer combinations.

As I suspected, this is the problem. Your views must be defined with named layer combinations to ever expect consistent behavior. Never trust a saved view that has "custom" as the layer combination name.

Karl

[Anonymous]

Is this o 8.1



Advice:
Newer use a release ending in 0 (as 9.0) unless you are non profit.

[Karl Ottenstein]

Adalbert wrote:
Advice:
Newer use a release ending in 0 (as 9.0) unless you are non profit.

You comment has nothing to do with this thread (as typical of your negative comments), and is negative without justification. 9.0R1/V1 is a stable, productive release and is not the topic here in any case. (The issue discussed applies to 8.1 as well.)

Karl

[Djordje]

Karl wrote:

Adalbert wrote:
Advice:
Newer use a release ending in 0 (as 9.0) unless you are non profit.

You comment has nothing to do with this thread (as typical of your negative comments), and is negative without justification. 9.0R1/V1 is a stable, productive release and is not the topic here in any case. (The issue discussed applies to 8.1 as well.)

To go even further back, it applies to 7.0 too.

[Anonymous]

Isn't defining view sets and defining layer combinations redundant? Doesn't a view set save the layer combination? I never see "custom" in the layer combinations. Layer combos are blank, or no layer combo is highlighted.

[Karl Ottenstein]

DHURD wrote:
Isn't defining view sets and defining layer combinations redundant? Doesn't a view set save the layer combination?

Yes and no.

A view set saves many things:
- layer combination (as a named combination, or whatever attributes each layer has at the time the view is saved)
- display combination (similar to above)
- scale
- zoom
- transparency in 3D

A 'named' layer combination is NOT the same thing as a combination of layers.

If you you save your layer settings as a named combination in the Layers dialog, and associate that NAME with a saved view, then that view will always reflect the info associated with that named combo. However you modify that comobo, the view will reflect it. Adding or deleting layers will not 'break' the values as you have been finding.

You can argue that perhaps it should work the way you are wanting it to. However, this is one of those cases of having to live with the way it is designed to work and to work that way. Further, it is self-documenting to use named Combos and makes it easier to know what is going on with your views IMHO.

Karl