Nice workaround Laci.

This wish is up there with referencing an external detail with the detail tool. If they can do one, they can do the other right?

Can't you just ride your bike over to the red fortress and ask them?

Cheers,
Link.

Link wrote:
Nice workaround Laci.

This wish is up there with referencing an external detail with the detail tool. If they can do one, they can do the other right?

Can't you just ride your bike over to the red fortress and ask them?

Cheers,
Link.

Yes, I will tell them. Iam going there several times a week because I am working for them on some materials that will come out in the future.
However, here is the other side of the coin: I started working with this method yesterday and in 30 minutes I managed to crash AC11 3 times. All I was trying to do was drawing Walls by clicking on points of this external Trace Reference and splitting Walls by lines contained in this external Trace Reference. So if you guys try it and see similar behavior, just be aware that it might be caused by this workaround. Maybe this much indirect referencing of data is not something the program is currently prepared for by code.
I am reporting this problem and wish to them now.

Since I needed to use this workaround solution in the last couple of days I could not help but find out what causes those crashes I wrote about in my previous post.
It is when you try to split an element and when you need to click the element which will split it:
IF
1. That splitter element is part of a Trace Reference
plus
2. The source of that Trace Reference is a Drawing placed on a Layout
THEN
there is a very good chance that it will crash ArchiCAD.

I will report this to GS.

Bier wrote:
For now:
Why not just copy “whatever” from source.pln, paste
onto “false” story of working.pln (either up or down) set the dynamite
charge, leave the room, come back when the smoke clears
and now you have a bunch of harmless lines that don’t contaminate
your schedules/views and have direct Trace Reference.

Yes, that could work, but I guess the Trace Reference feature was developed so we do not need such workarounds.
I prefer trying to use a feature to its max and then pushing GS for any needed fix rather than curdling my brain trying to think up workarounds.

Actually, I am in contact with GS about this crash. It seems it crashes only when the splitter element is a line. What we actually tried is this: when the splitter element was a Wall, everything was fine, when it was a line, it crashed.
A good piece of info to avoid these crashes until the fix comes.