Layer "ArchiCAD - master only"

[Electric Flute]

Once and a while AC creates a layer called "ArchiCAD - master only".
What is it for? Maybe related with Master layouts?
Does anyone also get this layer?
Thanks

[Anonymous]

Never seen it myself. Does it appear when you import layouts?

[Electric Flute]

AC creates it when I got to my layouts. So I delete it and then AC creates again each time I open my layouts.
I also checked if any elements in my layouts use this particular layer, but not.
Strange...

Win XP - AC10 int

[Rod Jurich]

Electric wrote:
Once and a while AC creates a layer called "ArchiCAD - master only".

Cadimage is the culprit.

You would have loaded some of their libraries. I'm still to work out what it is for.
What I've done is to create another file called Add-Ons REMOVED and moved a file named "MasterLayer.ini" out of the Add-Ons folder.
So far no problems and most important NO "Archicad-master only" created each time you delete it.
I find it most irritating when 3rd parties mess with layers/lines/fills and now Cadimage hijack Zone Category No 01 when you buy their site tools.

[Electric Flute]

Ron, you are right! Thanks a lot!

Yes, I also hate when 3rd parties mess with my standards. Cigraph also does this, I just got ArchiTerra 3 and it creates 4 new layers!! Yes, 4 new layers... At least It could give us an option to choose which layer to Architerra use.

We ArchiCAD users should tell Cadimage and Cigraph to not mess with our standards!

[__archiben]

it is required by cadimage tools, and yes - it is to do with master layouts. i think that it's how revision manager handles its revision objects (on a master layout) yet is able for it to display unique content when it is passed through to the layouts. or something like that.

whether or not you agree with add-on tools messing with your project attributes (i don't!), if you use cadimage tools you are better off not deleting it! whatever the case, this particular layer is always hidden automatically in model views . . .

also rod, i see you've moved the 'update all' add-on too! this is pretty important for being able to update multiple elements with different parameters - it lets the parameter scripts of multiple selected elements run separately with different outcomes depending on the element's current settings.

~/archiben

[Andy Thomson]

I don't suppose anyone can explain why the add-on was required for dwb aside from the update-all (and registration) function(s)? I much preferred it when it was an innocuous library object. (1_03, 3.5for9, etc).

[Rod Jurich]

andyro wrote:
I don't suppose anyone can explain why the add-on was required /......I much preferred it when it was an innocuous library object.

Isn't it a little odd Andy that we probabley will have to wait for young Ben to reply on their behalf

I would have thought that Tony Krepler would jump at the opportunity to address the forum.
He has, in the past, been helpful on a personal level. Come on Tony tell us all.

Seriously though, thought given to manuals and taking a little time to explain why they do what they do would also help.

Again I always come back to the fact that because you can program code does not tranform you into a proficient cad/bim practitioner.

What ever happened to KISS