Hopefully this is the correct place to post this.
Using internal elevations is painful, to be blunt. You can only move them, stretch etc by selecting the invisible line that is not automatically selected when you select the marker. Selecting the marker does not allow you to move the Int.Ele. The Internal Elevation tool does not allow you to use faded distant elements either. It is a worse version of the section tool in all ways in my opinion, to the point that I just use the section tool, but others still use the internal elevation tool and so must I. I think the tool needs to be at least as functional as the section marker, and to not have invisible lines you need to select to be able to move it.
Also, the naming and grouping of them seems to add extra unnecessary steps. You can have the group ID/Name, the actual Int.Ele. ID/Name, and the View Map ID/Name. Why do we need 3? The IE grouping in the project map is also fairly dysfunctional, a list would suffice if the ID's are correct, same as sections or elevations. Grouping them can happen in the View Map, but if absolutely required in the project map, make it functional, allow groups to be added to, or modified, however I think it should work the same as all the other parts of the project map. (Graphisoft is very good at making various tools function entirely different from the rest of the program every now and then, I advocate for the whole program functionality, menus etc to be homogenized.)
Often you will add internal elevations as required, which just creates a huge mess of single items taking up 2 lines because they are part of their own group because currently you cant add them to the existing groups. Or if you can it is some obscure work around that functions differently to the rest of the program.
Open