Fix rendering artifacts #215
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…red to avoid artifacts. It still does not render every frame
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In some cases, and apparently some configurations (it did not happen on my previous laptop), rendering artifacts would appear as a consequence of an optimization that avoids rendering if:
In particular, an idle window is not re-rendered; the same happens with mouse movement events which do not trigger a explicit render request from a widget.
As a workaround, once a frame render is requested, the library will render the next step too. It still does not render all the frames to reduce CPU usage, but incurs a (small?) penalty. I will investigate further solutions, but this seems to solve the issue for the time being.