Exactly!!! That was the other issue I was seeing.
This is currently how I do it with a block library I've built.
- Block drawn on 0 Layer/color white
- When inserted it automatically goes to the "NEW" layer
- User selects the button they need to move the object to "-56" or "Record Issue" Layers
This is for department who already have built all of their "Standard" layers into their template and they don't want to automate the process
for literally 100s of layers (well...think 100 hundred record issue layers).
They have 3 layers for each Record Issue layer.
New
56
Future
They literally have all of these layers already in the template with no filtering, customization, or anything. Can you say scroll scroll scroll your way?
They would rather require their users do it all manually. I'm trying to provide an example based on their current setup to convince them that automation saves them time and money. They either refuse to see it or as I suspect have, "My Way or the Highway" mentality. I've been cadding for 30 years and have never hear of anyone saying they want to do it manually. My approach has always been, minimize the number of layers in the layer dialog. The layers that are actively in the drawing should be the only layers in the layer dialog.
It's like talking to myself. I've convinced myself that my approach with this code is wrong and that I need to make them understand the benefits of automating their use of layers.
This is OK for objects but will throw an error with layers as you cannot set a layer colour to bylayer, and the code involves creating layers
If suffix is "-NEW" and
replaces "-NEW" with "-56" then
Will get you the base layer name and
will replace the old suffix with the new suffix. To reset to base layer name the new_suffix should be a zero length string (""). I think (strlen "") will return zero, if moving from base to a suffix, but i'm on LT at the moment so can't test. Tested and works