Keynote visibility (as seen in tech preview 2024)

[Jeliszej Korcsak]

Hey guys!

Watching the 2024 tech preview I immediately noticed a painful problem - that has been ongoing for ever - when the keynote functionality was presented. Did you all notice, that the keynotes, when added to selected object, are obscured by all the other model elements and zone fills?

I have been chasing this issue for years now, but my prayers are yet to be heard. Please, remove annotations, dimensions, labels and all such stuff from the ordering system of "send back and bring forward" stack. I could not think of any situation when I would want my annotation to be behind a wall or under a slab. It is just an extra task to always bring forward all my dimensions and lables before publishing my plans.

Am I the only one who is really bothered by this?

[Eric B]

I am the same and have been asking for the labels and dimensions to be added to the top of the display stack rather than having to select them and bring them to front

[Sunny75]

Yess please,this would be so beneficial!

[MinhNguyen]

Maybe I'm the minority here, but we need display order for annotations still, maybe not the whole 14 levels but at least 3-4 levels. We do structure core dimensioning (so fire stair/elevator) with cutout white fills instead of combining cropped views with different layer combos on layouts, and here having display order for annotations is important to control which ones go on top.

[Eric B]

Not saying do away with it but just make the labels, dimensions etc to the top of everything then being able to send it back if needed

[Barry Kelly]

Labels are on level 10 the same as text.

Keynotes are labels and are also on level 10.

So they should appear in front of other elements (slabs and walls = 7, beams = 9, lines = 9).

At least this is the case for me.

Barry.

[Jeliszej Korcsak]

This is the case when you leave everything on default. But sometimes there are situations when you have to shuffle the order.

In teamwork, on very large projects, we always have to add a step before publishing our documentation, to bring all dimensions, annotation and text forward, because it just slips behind some stuff. I think this is a big deal, because even the live event had the same issue when showing off keynotes. Also, it is really straightforward for most of us, that dimensioning and annotation always have to be visible no matter what.

I understand that tehre may be other workarounds and workflows where you got accustomed to hiding some of the text for different reasons, so what I propose is a switch in the settings, that moves all dimensions and annotation to the virtual topmost level so that they never can be obscured. And you could turn off this "forced behavior" if you are one of those who needs them in the classical order stack.

[Barry Kelly]

---

@Jeliszej Korcsak wrote:

This is the case when you leave everything on default. But sometimes there are situations when you have to shuffle the order.

---

So there is no problem with the software then?

You are taking control and changing the default order, so therefore you are responsible for the display order.

Or are you saying that out of the box, the display order is messed up?

I have not found this to be the case.

Only when I start messing about with the display order of elements do I start having issues I have to watch out for.

Maybe in the tech preview video, some of the other elements had been brought forward?

This may be why the keynotes appeared behind the elements.

I just re-watched the keynote section in the tech preview webinar and I didn't notice any keynotes going behind any other elements.

Barry.

[Eric B]

 For me it definitely happens when I start messing with the display order for sure - but we do tend to mess with it quite a bit

When I do I typically select an item and bring to front rather than multiple bring forwards which of course brings things into the text view layer

It would be nice that a bring to front brings all objects to the top layer - 1 so that it preserves the text at the top by default but nothing to stop it being moved down if need be

[marco conti]

yes, I totally agree.