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
If you look at the title, and picture below - the yellow tooltip is very convenient during achievement development and is shown when you mouseover on memory value. The tooltip stops showing up or may show up for a moment and disappear, if there's an Memory Bookmarks window open that has an updating value (in my case it's frame count). I assume it's some windows-based rerendering/update caveat being in play here.
Issuing this on
RALibretro 1.3.8
Windows 10 x64 21H1
If you have a hint on what the issue might be and where to look at to fix, I could try handling it myself
The text was updated successfully, but these errors were encountered:
This problem does not occur in the other standalone emulators.
This is somehow a caused by the interaction between SDL2 and the Windows API, and RALibretro uses SDL2 as its graphics layer.
We are already explicitly calling RedrawWindow to get the tool windows to repaint as the SDL2 message loop doesn't promote the WM_INVALIDATE messages into WM_PAINT messages as expected. I suspect something similar is happening with the tooltip, for which we don't forcibly call RedrawWindow.
For reasons that are completely unclear, the InvalidateRect calls for the memory viewer and search results are only promoted to a WM_PAINT event when other events are in the queue (i.e. WM_MOUSEMOVE). This behavior appears to be SDL-specific, and I can't figure out why.
If you look at the title, and picture below - the yellow tooltip is very convenient during achievement development and is shown when you mouseover on memory value. The tooltip stops showing up or may show up for a moment and disappear, if there's an Memory Bookmarks window open that has an updating value (in my case it's frame count). I assume it's some windows-based rerendering/update caveat being in play here.
Issuing this on
If you have a hint on what the issue might be and where to look at to fix, I could try handling it myself
The text was updated successfully, but these errors were encountered: