Tooltip gets triggered when leaving modal dialog #88721

New Issue

Leon Zandman · 2021-06-01T16:51:26+02:00

Leon Zandman commented

2021-06-01 16:51:26 +02:00

System Information
Operating system: macOS-11.4-arm64-arm-64bit 64 Bits
Graphics card: Apple M1 Apple 4.1 Metal - 71.6.4

Blender Version
Broken: version: 2.93.0 Beta, branch: master, commit date: 2021-05-31 15:30, hash: 46a14bd6a3
Worked: -

Short description of error
When moving the mouse cursor outside of a modal File Dialog, sometimes a tooltip is triggered when it shouldn't. Probably an edge detecting bug.

Exact steps for others to reproduce the error
I've included a GIF recording with this bug report that hopefully explains the behavior I noticed. Here are some steps to reproduce:

Start Blender and select File -> Open to display the File Dialog.
Ensure the "Recent" section on the left of the dialog has multiple entries.
Resize the File Dialog so that the "Recent" section is truncated by the bottom border of the File Dialog. It should be truncated so that it displays only the top few recent folders (i.e. the other folders, the little disclosure triangle and the section's bottom drag bar shouldn't be visible).
Hover the cursor over the File Dialog and move it outside of the dialog, making sure you exit the dialog through the bottom part of the "Recent" section.
Watch as the "Active Recent Folder" tooltip gets triggered/displayed while the mouse cursor is outside of the dialog. This shouldn't happen!
Now enlarge the bottom part of the File Dialog, so that the "Recent" section is no longer truncated and fully displayed (including its disclosure triangle and drag bar).
Repeat step 4 and notice the tooltip doesn't get triggered anymore! This is the desired behavior.
Resize the bottom part of the File Dialog so that the "Recent" section is again truncated, but this time don't truncate its bottom part (i.e. the disclosure triangle should be visible).
Repeat step 4 and notice the tooltip again doesn't get triggered anymore! This is again the desired behavior.

Conclusion
It looks like the the File dialog somehow doesn't properly detect the mouse has exited the dialog when it exits directly from a section's contents, thereby not crossing over the section's border/other UI parts.

I hope this makes some sense ;-)

**System Information** Operating system: macOS-11.4-arm64-arm-64bit 64 Bits Graphics card: Apple M1 Apple 4.1 Metal - 71.6.4 **Blender Version** Broken: version: 2.93.0 Beta, branch: master, commit date: 2021-05-31 15:30, hash: `46a14bd6a3` Worked: - **Short description of error** When moving the mouse cursor outside of a modal File Dialog, sometimes a tooltip is triggered when it shouldn't. Probably an edge detecting bug. **Exact steps for others to reproduce the error** I've included a GIF recording with this bug report that hopefully explains the behavior I noticed. Here are some steps to reproduce: 1. Start Blender and select `File -> Open` to display the File Dialog. 2. Ensure the "Recent" section on the left of the dialog has multiple entries. 3. Resize the File Dialog so that the "Recent" section is truncated by the bottom border of the File Dialog. It should be truncated so that it displays only the top few recent folders (i.e. the other folders, the little disclosure triangle and the section's bottom drag bar shouldn't be visible). 4. Hover the cursor over the File Dialog and move it outside of the dialog, making sure you exit the dialog through the bottom part of the "Recent" section. 5. Watch as the "Active Recent Folder" tooltip gets triggered/displayed while the mouse cursor is outside of the dialog. This shouldn't happen! 6. Now enlarge the bottom part of the File Dialog, so that the "Recent" section is no longer truncated and fully displayed (including its disclosure triangle and drag bar). 7. Repeat step 4 and notice the tooltip doesn't get triggered anymore! This is the desired behavior. 8. Resize the bottom part of the File Dialog so that the "Recent" section is again truncated, but this time don't truncate its bottom part (i.e. the disclosure triangle should be visible). 9. Repeat step 4 and notice the tooltip again doesn't get triggered anymore! This is again the desired behavior. ![Blender-Tooltip.gif](https://archive.blender.org/developer/F10152948/Blender-Tooltip.gif) **Conclusion** It looks like the the File dialog somehow doesn't properly detect the mouse has exited the dialog when it exits directly from a section's contents, thereby not crossing over the section's border/other UI parts. I hope this makes some sense ;-)

Leon Zandman commented

2021-06-01 16:51:26 +02:00

Added subscriber: @Zandman

Harley Acheson commented

2021-06-16 00:09:27 +02:00

Added subscriber: @Harley

Harley Acheson commented

2021-06-16 00:09:27 +02:00

Answering technically since I know you have submitted some patches recently.

Blender's event loop generally sends messages only to the active area, the one currently under the mouse. So the area is getting messages while your mouse is over it, but then they stop when you leave. This design does mean that we can quite often miss notifications that you have left an area, if knowing that is important. An easy way to see this behavior (also in File Manager) is to highlight one of the file names, quickly move your mouse out of the area at the closest edge, and see that it can still be highlighted.

This normally doesn't cause a lot of real problems, generally just the odd thing highlighted wrong for a while. When it does matter though, there is a callback that can be used. The ScrArea has a member called "type", which is a SpaceType struct. One of the callbacks there is "deactivate". So you can write a handler to clean up whatever you want. An example of it being used is in space_outliner.c

Answering technically since I know you have submitted some patches recently. Blender's event loop generally sends messages only to the active area, the one currently under the mouse. So the area is getting messages while your mouse is over it, but then they stop when you leave. This design does mean that we can quite often miss notifications that you have left an area, if knowing that is important. An easy way to see this behavior (also in File Manager) is to highlight one of the file names, quickly move your mouse out of the area at the closest edge, and see that it can still be highlighted. This normally doesn't cause a lot of real problems, generally just the odd thing highlighted wrong for a while. When it does matter though, there is a callback that can be used. The ScrArea has a member called "type", which is a SpaceType struct. One of the callbacks there is "deactivate". So you can write a handler to clean up whatever you want. An example of it being used is in space_outliner.c

Pratik Borhade commented

2021-06-23 12:19:30 +02:00

Added subscriber: @PratikPB2123

Pratik Borhade commented

2021-06-23 12:19:30 +02:00

Changed status from 'Needs Triage' to: 'Confirmed'

Pratik Borhade commented

2021-06-23 12:19:30 +02:00

Guess we can mark this a low priority issue.

@Harley , please edit the status if you feel this is not a bug :)

Guess we can mark this a low priority issue. @Harley , please edit the status if you feel this is not a bug :)

Leon Zandman commented

2021-06-23 14:01:15 +02:00

I don't know if it's related, but I have experienced several times where I perform actions like moving a node in the Compositor or moving the mouse to scale an object, where the mouse leaves the windows. In theory you should be able to continue moving the mouse and the operation will continue too. But in practice often the operation goes haywire and the scale factor increases very much or the node shoots off the screen. I've seen this reported in other bug reports too, so it looks like some mouse messages get lost when the mouse crosses window borders.

Philipp Oeser removed the

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Tooltip gets triggered when leaving modal dialog #88721