Read only Layer States?

[Anonymous]

Is there any way to lock a LayerState? We have some "office standard" layer
states setup, but users tend to change them for their personal use, which
ruins them for downstream use. As a result, lots of those downstream users
won't even bother with Layer States anymore.What I would like to do is
create some office standard layer states and lock them, but allow user layer
states also. Another option would be to automatically reload any present
office standard layer state from LAS files, but I guess that becomes a
question for the Customization groups.

So, anyone else have this problem? And have you found a way to solve it?

Best,
Gordon

[Anonymous]

Gordon Price wrote:

> Another option would be to automatically reload any present
> office standard layer state from LAS files ...

I would say thats the best solution you have. Attach it to startup
code or maybe a reaction to drawing save.

Terry

[Anonymous]

we have made excellent use of lisp routines that freeze, lock, unlock, thaw
etc layers in model, pspace, viewports, xrefs or not etc people tend to
use these because they work whether all of out layers are used or not.
layer states requires manipulation of states if you add a bunch of layers
--
Jamie Duncan

"Maybe the Hokey Pokey is REALLY what's it all about"
"Gordon Price" wrote in message
news:A7BC15BA889FD2DF1C684A60FEFF652F@in.WebX.maYIadrTaRb...
> Is there any way to lock a LayerState? We have some "office standard"
layer
> states setup, but users tend to change them for their personal use, which
> ruins them for downstream use. As a result, lots of those downstream users
> won't even bother with Layer States anymore.What I would like to do is
> create some office standard layer states and lock them, but allow user
layer
> states also. Another option would be to automatically reload any present
> office standard layer state from LAS files, but I guess that becomes a
> question for the Customization groups.
>
> So, anyone else have this problem? And have you found a way to solve it?
>
> Best,
> Gordon
>
>

[Anonymous]

"Jamie Duncan" wrote in message
news:AD7060BE46E7BFD67C83761CF5B58F87@in.WebX.maYIadrTaRb...
> we have made excellent use of lisp routines that freeze, lock, unlock,
thaw
> etc layers in model, pspace, viewports, xrefs or not etc people tend to
> use these because they work whether all of out layers are used or not.
> layer states requires manipulation of states if you add a bunch of layers

My hope is that layer states that contain all office standard layers, and
consistantly produce office standard results, would lead to 1: more use of
layer states and 2: compliance with office standard layers because not doing
so breaks your layer states. Also, I can do it with minimal programming 😉
It sounds like the answer is to automate. So, comments welcome on this
proposal:

Office standard layer states are prefixed with office initials and an
underscore, eg THA_Floor_Plan.
Project standard layer states are prefixed with the job #, eg
2003.12_Furniture_Plan.
User layer states are prefixed with user initials, eg GWP_Electrical.

Part of S::STARTUP would rebuild all office standard & project standard
Layer States from file, ignore layer states that start with three letters
and an underscore, and delete everything else. A cleanup lisp routine would
allow the user to delete all their layer states by entering their initials,
and another routine available to the CAD Manager deletes all non standard
layer states.

Anyone have any thoughts on this approach?

Gordon

[Anonymous]

I wonder why user layer states are needed, I mean if you have power panels
on a given layer, wouldn't that be the same for everyone?
Just curious/

We use the AIA short form - it allows easy grouping of layers by object type
A: architectural
C: civil
E: electrical
Makes it very easy to toggle layer groupings on or off , or do layer states
etc

Jamie Duncan

"Maybe the Hokey Pokey is REALLY what's it all about"
"Gordon Price" wrote in message
news:B38C450B62991E2DC5A599B51723C2E7@in.WebX.maYIadrTaRb...
>
> "Jamie Duncan" wrote in message
> news:AD7060BE46E7BFD67C83761CF5B58F87@in.WebX.maYIadrTaRb...
> > we have made excellent use of lisp routines that freeze, lock, unlock,
> thaw
> > etc layers in model, pspace, viewports, xrefs or not etc people tend
to
> > use these because they work whether all of out layers are used or not.
> > layer states requires manipulation of states if you add a bunch of
layers
>
> My hope is that layer states that contain all office standard layers, and
> consistantly produce office standard results, would lead to 1: more use of
> layer states and 2: compliance with office standard layers because not
doing
> so breaks your layer states. Also, I can do it with minimal programming 😉
> It sounds like the answer is to automate. So, comments welcome on this
> proposal:
>
> Office standard layer states are prefixed with office initials and an
> underscore, eg THA_Floor_Plan.
> Project standard layer states are prefixed with the job #, eg
> 2003.12_Furniture_Plan.
> User layer states are prefixed with user initials, eg GWP_Electrical.
>
> Part of S::STARTUP would rebuild all office standard & project standard
> Layer States from file, ignore layer states that start with three letters
> and an underscore, and delete everything else. A cleanup lisp routine
would
> allow the user to delete all their layer states by entering their
initials,
> and another routine available to the CAD Manager deletes all non standard
> layer states.
>
> Anyone have any thoughts on this approach?
>
> Gordon
>
>

[Anonymous]

"Jamie Duncan" wrote in message
news:EC6F40EB838BB56106BC3F532E6424BD@in.WebX.maYIadrTaRb...
> I wonder why user layer states are needed, I mean if you have power panels
> on a given layer, wouldn't that be the same for everyone?
> Just curious/
It is situational. For example, my "standard" electrical plan & lighting
plan do not include furniture. However, on a particular project I might want
to create a layer state with the furniture on and screened so I can layout
lighting and outlets with respect to the furniture. However, when I actually
plot the sheet I might not want that on. Or I might decide I do and make my
temparary standard a project standard.
Also, given that people tend to make all their own layer states now, I
figure if I show them that they still can, I will get less fight. Hopefully
they find that the office standards now work so well they don't need to make
their own.

Gordon

[Anonymous]

Pink slip should work.

I may not like the Standards at work, but I follow them.

Later
Kirk