-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Persistent Frame in Profile Window #25
Comments
Current hypothesis: Check Profile::loadprofile, even though it's got a mutex locking the whole method, it could be called with some arguments, block, those arguments become out of date, and then the method unblocks and loads the wrong set of points. Unsure though how this could cause this particular bug. |
Observed to not be restricted to getting a new profile. Has now occurred when just changing the profile location and moving in the 2d overview window without refreshing the profile. |
Turns out to occur when: the profile is drawn on the overview, and a point is queried with right-click. |
Mish-mashed BoxOverlay into doing the job of overlaying the point selection box rather than the LagDisplay::overlayBox method (which probably causes this). That means:
|
Sometimes, somehow, the profile get's stuck on one particular frame. Refreshing the frame by moving around or zooming though, reveals the frame the user would expect before the program flickers back to the frame it's stuck on.
The text was updated successfully, but these errors were encountered: