-
Notifications
You must be signed in to change notification settings - Fork 83
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
screen glitching and redraw prioritization #97
Comments
@scanner-darkly has a fix for this in Maybe @scanner-darkly and @burnsauce can coordinate to get the changes in? |
Added some comments here: https://llllllll.co/t/new-teletype-operators-and-features/9076/191?u=sam |
there were changes made both in the these changes include:
teletype changes are here: scanner-darkly@c47eaaf they include:
testing: with @samdoshi official 2.0 i still managed to lock it reliably and quickly with extreme scenario (10ms metro, audio rate triggers, lots of i2c reading and writing in metro). with the above changes i wasn't able to get it to crash (i ran it for over 40 hours). |
for screen/keyboard responsiveness we just need to update teletype, for i2c stability both teletype and trilogy/ansible will need to be updated. |
forgot to add, my change was essentially a super simple implementation of having a higher priority queue for screen/keyboard updates. i think @burnsauce had some ideas on how to do this as well. |
Yeah, I'd like to create a proper scheduler to handle as many of the teletype's jobs as possible with predictable performance and timing for critical functions. |
perhaps we should do an intermediary (say 2.0.1) release that fixes this
prior to the 2.1 feature burst?
i can attempt this today.
…On Wed, Sep 13, 2017 at 7:13 PM, Poindexter Frink ***@***.***> wrote:
Yeah, I'd like to create a proper scheduler to handle as many of the
teletype's jobs as possible with predictable performance and timing for
critical functions.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#97 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAPEcE-d1ai0uibRWTxHVQhbeirdrIfqks5siGGUgaJpZM4PWGM_>
.
|
2.0.1 did indeed solve this problem, so the issue can be closed. |
screen redraw needs optimization
partial redraws moving between edit and tracker, for example
The text was updated successfully, but these errors were encountered: