Tooltips sometimes drawing out in left field


#1

Using a TooltipWindow without a parent component, we often observe the following:

  • A tooltip is shown on top of our plugin UI (as expected, so far so good)
  • The mouse is moved quickly outside of the plugin UI
  • A new tooltip appears, sometimes even on a secondary display, for the last component the mouse traversed over. That last-traversed component still appears hovered-over, although the mouse is far far away. In many cases, the tooltip (and mouse cursor) is >1000px from our plugin UI and from a user perspective, is very strange.

Has anyone else seen this behavior? Are there any solutions?


Menu selection disko in PT
BUG: MouseListener::mouseExit doesn't get called if mouse moves quickly between components
#2

I might be wrong but I have a suspicion that the component still appearing to be hovered over could be related to this Mouse-Exit Bug


#3

Definitely seems likely to me. The workaround we used there would definitely not work for the tooltips, unfortunately. This one seems like it will require a JUCE fix or our own rewrite of the tooltip window class.


#4

This involves some code that Ed has been working on recently. He is on holiday but should be back tomorrow.


#5

37c243b should fix this issue and also the issue with components remaining hovered-over when the mouse leaves the plug-in window. Can you confirm that it works for you?


#6

Sorry to say, https://github.com/WeAreROLI/JUCE/commit/37c243bb491e31e84fa13ccbecbab5b6c51ebb28 doesn’t seem to fix it for us. FWIW, it seems easiest to make happen in AAX.


#7

Do you apply any scaling to the plugin?


#8

No, other than the scale factor for retina / high-DPI displays. We’ve observed it for both retina and non-retina displays.

In general, the tooltips work great and display with the correct scaling and positioning.


#9

I think Ed’s fix was good. He just forgot to also add it to AAX (I don’t think he has ProTools on his machine). I’ve pushed the necessary change to develop with commit 7d98da9.

Can you confirm that commits 37c243b and 7d98da9 fix the issue?


#10

It worked! Thank you!