I was operating in JUCE 3 before and have just now recently updated. Everything with the update went smoothly except for one component - the ToolTipWindow. It had originally been working for me in JUCE 3 but with the update to JUCE 4 modules, it no longer displays correctly. I have updated to the various virtual functions now used (getTooltipBounds override, etc).
To describe the behavior: It appears, drawn correctly, but then quickly disappears. The remnant of it still is shown (the dropdown + 1px border) but the body of it is not shown. Breakpointing through Juce_TooltipWindow, it never calls the hidetip() function. Below is the actual uploaded image of what it appears like. Before it actually disappears, I breakpointed and it gets lost in the DefWindowProcW function call in WinUser.h.
It happens, regardless of the component used. Generally speaking, though, the tooltips are generated from buttons located on a TopLevelWindow.
Has anybody had an issue like this before? Anybody know where to go from here to investigate this?
Additionally: The TooltipWindow appears like this regardless of if I moved the mouse or not. As in, if I set it to appear in 2 seconds, and wait 2 seconds without moving the mouse, it appears and then the body disappears to have it remain like above. Therefore, it has nothing to do with the mouse movement itself (there was the addition of the mouse listener in 3 to 4, and I was wondering if it had caused this issue).
Another observation is that the TooltipWindow never grabs focus (focus always remains on the button, even when I hover in the TooltipWindow area.)
Setting the parent to the TopLevelWindow corrects this entire problem. However, I have multiple TopLevelWindows with Tooltips. As a result, I don’t have the ability to set the parent to just a single TopLevelWindow and expect it to work across the board.