to op Discussion click here: https://archicad-talk.graphisoft.com/viewtopic.php?f=20&t=70172#p313012 n ö
I never understood why archicad doesn't have this feature. Very surprising. Even relatively simple programs such as photoshop have the layer display feature of the selected element, while the absence of this in a complex program like archicad is a big handicap.
In a nutshell: through hundreds of layers, for the purposes of -changing layer name; changing it's priority level; duplicate it as a sequel to a close name for a reason; delete it etc.- layer palette should show [must make highlighted] automatically the selected elements layer when it opens.
just like in the "building materials" palette.
Building material pallet shows inside(makes highlited) when i choose something before opening the palette. )
Even having the layers searchable/filterable by name would help.
In a decent sized project you need loads of layers to properly control the various plan views and/or options. It would make life so much easier to have the current layer auto selected in the layer palette. It makes me wonder sometimes if anyone at Graphisoft has used the programme on a real project!
runxel wrote: Let's please just abandon layers alltogether....
There are already properties, let us just filter by that, GS!
In case you and others haven't notice, you can vote for this here.
Hi Mr. Braza, im very very used to layers, which is something i carried from the autocad days and made my transition to Archicad easier. Ive been reading this intention of eliminating layers for some time now. I would like to ask, generally speaking, what would be the advantages of using properties or clasifications over layers? I can intuitively see that they could be better, but cannot see how.
IMO I can only see advantages. Like:
1. Coooonnnnnssssiiiisssssttttteeeeennnnnncccccccyyyyyyyyyy... Ahummmmmmmm! As it would concentrate Layers, Layer Combo, Renovation Filter, Partial Structure Display. These all could be converted to properties (which in reality is what they are);
2. It eliminates the need for innumerous layers to accommodate a proper project documentation workflow;
3. Gives the user the total power to control visibility of all the elements of a virtual building. As today we can create any Classification and Property, but we can't apply them to 2d elements. i.e.: You can hide any specific element that could also share the same layer and/or Renovation Filter and/or Structural role with others;
4. Allow us to easy create phasing, construction simulation and versioning schemes for any project;
5. If also applied to Complex Profiles would allow for total easy control of complex structures and elements;
6. The process of applying Classifications is much more straight forward than applying Layers. With Classifications you can apply innumerous Properties to a single element with just one click.
And let's not forget that you can put multipe classifications on an element, but can only assign one layer!
This often means that you have the same thing multiple times, just on different layers, because they are such a rigid and outdated concept (which comes from physical layers; tracing paper stacked upon each other), and there is just no other way around, because layers are the main thing that governs visibility (together with reno, but if you are in a reno project, it renders this approch unusable; and let's better not talk about psd).
Lucas Becker | AC 27 on Mac | Editor at SelfGDL | Developer of the GDL plugin for Sublime Text | «Furthermore, I consider that Carth... yearly releases must be destroyed»