We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Using trees in GUI code seems too much.
The text was updated successfully, but these errors were encountered:
And we could also consider hardware acceleration: http://wiki.osdev.org/Accelerated_Graphic_Cards
But QEMU defaults to emulate "cirrus" graphics card, without much support for acceleration... It must be our drawing algorithm that could be enhanced.
After some experiments, I found that making better use of cache might help. But that requires nested loops.
I am working on loop exchange techniques in Compositor::drawSingle
Sorry, something went wrong.
Faster in fded70c
Now the lag seems to be due to long critical sections.
Also after exchanging the loops, some new bugs appear in compositor (redrawing mouse will affect the windows beneath it).
Maybe we should not exchange the loops but check the conditions in advance, and use a temporary list of elements to draw.
No branches or pull requests
Using trees in GUI code seems too much.
The text was updated successfully, but these errors were encountered: