You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The intent is that if the mouse has moved 5 pixels reset the tooltip timer. However, mm->get_relative() gets the relative motion to the last inputevent, not in relation to where the timer was started. So it means like 5 pixels per frame (or however often inputevent are triggered).
So the bug is a bit more severe, tooltip appears even if the mouse is in steady motion.
I think solution to this would be either use the initial version of #95846 (check that relative motion != zero), or if we really want that 5 px leeway, save the starting position. But I think zero movement is good enough, the situation is different from doubleclicking, since to show tooltip you can just not touch the mouse (vs accessibility problem of doubleclicking without moving mouse).
Edit: After testing the first solution I mentioned, it seems to fix the problem I found but not the original issue. I still think it's going to be one solution that fixes both of these, so I won't open a separate issue just yet.
Edit2: I tried implementing the second solution and it seems to work well. There wasn't even need to introduce a new property for tracking the position, I hijacked the existing gui.tooltip_pos 👌
Tested versions
4.4 dev 5675c76
Not reproducible in 4.3
System information
Windows 10.0.19045 - Vulkan (Forward+) - dedicated NVIDIA GeForce GTX 1060 (NVIDIA; 31.0.15.4633) - Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz (8 Threads)
Issue description
If you move cursor before hovering over something with tooltip, the tooltip can appear at older mouse position.
WcVqifhu8C.mp4
Steps to reproduce
Minimal reproduction project (MRP)
N/A
The text was updated successfully, but these errors were encountered: