Graphic override - layer combination problem

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2017-07-12
05:51 AM
- last edited on
2023-05-23
04:14 PM
by
Rubia Torres
I am trying to set up a rule that changes the pen colour of an object when a certain layer combination is turned on.
But no matter what layer combination I have set, the colour is still overridden (see attached image).
Am I barking up the wrong tree in expecting this to work?
Barry.
Versions 6.5 to 27
i7-10700 @ 2.9Ghz, 32GB ram, GeForce RTX 2060 (6GB), Windows 10
Lenovo Thinkpad - i7-1270P 2.20 GHz, 32GB RAM, Nvidia T550, Windows 11

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2017-07-12 05:56 AM
Barry.
Versions 6.5 to 27
i7-10700 @ 2.9Ghz, 32GB ram, GeForce RTX 2060 (6GB), Windows 10
Lenovo Thinkpad - i7-1270P 2.20 GHz, 32GB RAM, Nvidia T550, Windows 11

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2017-07-12 06:03 AM
What is the difference between "Layer" and "Layer Name" except with the latter you must manually type the name in and it gives you more choices rather than just "is" and "is not".
More choices but it doesn't work.
Barry.
Versions 6.5 to 27
i7-10700 @ 2.9Ghz, 32GB ram, GeForce RTX 2060 (6GB), Windows 10
Lenovo Thinkpad - i7-1270P 2.20 GHz, 32GB RAM, Nvidia T550, Windows 11

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2017-07-12 08:28 AM
Barry wrote:Hi Barry, because ARCHICAD Layer is a special layer I think it’s not as simple as typing in the name as you see it. Try typing another layer that you have created yourself. Also, Layer Name allows you to include a bunch of layers using contains or starts with. But the Layer just allows one layer to be picked, and you’d need to manually add more criteria to include more layers - which can be more cumbersome.
And then oddly if I change the rule to "Layer Name" it doesn't override at all.
What is the difference between "Layer" and "Layer Name" except with the latter you must manually type the name in and it gives you more choices rather than just "is" and "is not".
More choices but it doesn't work.
James.
Graphisoft Senior Product Manager

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2017-07-12 08:42 AM
Yes using a different layer worked - I didn't think that "ARCHIAD Layer" only appears to be called "ARCHICAD Layer" but that is not it's real name as far as Archicad is concerned (that has caught me out in GDL before).
But it is my initial problem I would like to clarify - the use of layer combinations.
This would be perfect if it id work as I want to hide specific objects in a specific layer combination without having to create a new layer that I can hide.
Just experimenting with making a new classification and hiding (making white) if that classification is set.
Seems to be working fine, but it would be so much easier if the layer combination worked as that is already set up in all my jobs and all I have to do is add the Graphic Override.
Barry.
Versions 6.5 to 27
i7-10700 @ 2.9Ghz, 32GB ram, GeForce RTX 2060 (6GB), Windows 10
Lenovo Thinkpad - i7-1270P 2.20 GHz, 32GB RAM, Nvidia T550, Windows 11

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2017-07-12 11:33 AM
The override is either always on or always off, as far I can tell.
POSIWID – The Purpose Of a System Is What It Does /// «Furthermore, I consider that Carth... yearly releases must be destroyed»
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2017-07-12 01:07 PM
For instance if your object layer is hidden in combo B then although it is visible in selected combo A then it may not be affected by the GO and if visible in combo B then it would be affected by the GO.


- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2017-07-12 01:55 PM
DGSketcher wrote:Never worked in AC20 as well. So this bug is not specific to 21.
Hi Barry, I haven't had a chance to spend time with AC21 yet but have you considered that the logic of the conditions may be different.
POSIWID – The Purpose Of a System Is What It Does /// «Furthermore, I consider that Carth... yearly releases must be destroyed»

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2017-07-13 03:16 AM
DGSketcher wrote:It should have nothing to do with the layer visibility (except the obvious if the layer is on the object shows, if it is off then it won't).
Hi Barry, I haven't had a chance to spend time with AC21 yet but have you considered that the logic of the conditions may be different. Could it be that the conditions check the visibility of the layer within the named combination only and not which layer combination is currently set?
For instance if your object layer is hidden in combo B then although it is visible in selected combo A then it may not be affected by the GO and if visible in combo B then it would be affected by the GO.
To my understanding it should simply be that (assuming the object layer is visible in all layer combinations) if the layer combination is active then the object should be overridden.
If a different combination is active then the object will not be overridden.
This is what I am trying to determine - is this what should be expected - before I report this a s a bug.
Barry.
Versions 6.5 to 27
i7-10700 @ 2.9Ghz, 32GB ram, GeForce RTX 2060 (6GB), Windows 10
Lenovo Thinkpad - i7-1270P 2.20 GHz, 32GB RAM, Nvidia T550, Windows 11
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2017-07-13 12:19 PM
I did find this page which kind of supports my option but isn't totally clear and I still haven't had a chance to test it so you you may be right and it could be a bug...