Closed
Conversation
Closed
Contributor
I wonder if it could work with putting two canvas widgets in the app, one presenting as screen and the other as bitmap? might be an easy way to compare responsiveness for example. |
Member
Author
|
Fix included in #138 |
This file contains hidden or 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
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.
utils/cube.pyto use low-power adapter to select intel driver.cube_qt.pyto easily switch between bitmap and screen.It looks like once
paintEnginereturns something, qt goes with that, so we should not default to returning the normal engine. This will at least make 'screen' work. For 'bitmap' it looks likepaintEngineis never even called (?)Would be good to test this out on a few systems and platforms.
If this works, I'll merge
async-bitmapand prepare a new pr with the fix (but it will be a bit different).