Hi, I am newbie and testing Nexus ultimate.
Opening and closing my main-dock when mouse moves to screenegde and leaves dock works perfekt.
When I hoover over the subdock-icon, it opens, but when now I leave this subdock without click, it does not close.
Is this correct? Is it my fault?
I would expect, that it closes as fast as the main-dock. How could I achieve that?

Techlobo, is that you?

Seriously now, this was just discussed recently. Read my response in this post HERE (second part of the post) and TechLobo's counter-arguments HERE.

Essentially closing as you mouse away would be VERY prone to sub-docks, etc, closing automatically when you do not actually intend to do so. And trust me, this would be a hell of a lot more annoying than having to close a sub-dock that opens automatically on mouse over by clicking somewhere else.

This is, of course, debatable, so feel free to join forces with Techlobo in trying to convince me otherwise (e.g. adding an option that makes sub-docks, grid-stacks, etc, auto-close as you mouse away).

Just a week ago was discussed IIRC! And the conclusion certainly was that it would be a bad idea. Actually, I think a *very* bad idea - whichever would be the default, it would be a PITA for half of users. And we all know how brilliant most users are at exploring/changing settings without extensive hand-holding! Could be a real support nightmare too.

Nope not me - although its an interesting coincidence!

I don't think it would be a bad (or very bad) idea, especially if the option is to enable it - I suspect most users don't really get into the detailed settings very often.

Anyway I've already said my piece.

Thanks to Jorge,
I studied the links, but obviously I am not common with all the features of Nexus. So it is hard to understand, why subdocks behave different to maindocks and why it makes trouble, to close a subdock by the mouse-leave-event.

See, that you think the sub-dock should close automatically upon the mouse leave event (i.,e. as soon as the pointer leaves the sub-dock) already shows you don't understand the implications - but don't feel bad, most people wouldn't either: they know what they want, but not what is actually required to get it.

We humans are not computers able to make mouse pointers travel in a perfect straight line that never wanders off target. As we move the pointer, many time we accidentally go off the intended path, overshoot or undershoot the target, etc... immediately closing the sub-dock on a mouse leave event is completely unforgiving of our "humanity" lol

The fact is that the mouse pointer first has to travel from the parent dock to the sub-dock. This already poses problems: if the sub-dock is horizontal, reaching out for the icons at the edges of the sub-dock might mean that the mouse pointer first passes over a neighbor icon in the parent dock (which would result in the sub-dock automatically closing, especially if that icon also opens a sub-dock).

This is one of the reasons why having a 0 ms delay to automatically opening or closing sub-docks is usually a very bad idea.

Then, once the mouse pointer is over the sub-dock, it has to travel to the target icon. Here too problems may occur, you might accidentally make the pointer go off the sub-dock while attempting to reach the target, even if only for an instant. This is another reason why closing a sub-dock based on a mouse leave event is a terrible idea.

For this not to be an exercise in rage inducing frustration, mitigations must be added, such as delays in automatically opening and closing sub-docks, and triangular "travel zones" that do not trigger closing events. These mitigations are very difficult to get right, and even then are just that, mitigations.

So, to avoid all that it's much simpler to keep a sub-dock open until you deliberately open another, or until you deliberately dismiss it by clicking somewhere else. This way the sub-dock only closes when you actually want it to close, and not accidentally while you are trying to do something else.

There are other reasons, which I described in my other post. This is just for you guys to understand that things under-the-hood are normally not as simple as they might appear to be at first glance.

Thanks, your right. But in the main dock you handle that leave-event (with delay), don't you? Seems to be much more complicated for subdocs...: pity

Dare one hope that this is the end of this subject? It really makes no sense at all. This is not talking about a single class of object but several. Docks are one class, Sub-Docks quite another, as are the others. Live with it!

So its too hard

OK, I'll not ask again.

As Nexter says I will 'Live with it!'

Good to see. Glad we're all sorted, @techlobo.