-
-
Notifications
You must be signed in to change notification settings - Fork 320
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.Clear
— Flickering on Windows
#647
Comments
So 576 only fixed POSIX. The fix is simple. Stay tuned. |
Thanks, @gdamore! Looks like this solves the problem. (As a minor note, it looks like the cursor still flickers on Windows even when the screen content remains the same and the cursor's position doesn't change. But I haven't looked into this in detail so I don't know if this is a |
I suspect that we need to hide the cursor when drawing. In the past we drew using a direct API, but now that we're using the escape codes to do this, we probably need to add the logic to hide the cursor for a redraw. |
Following up on this comment, I noticed that calling
Screen.Clear()
prior toScreen.Show()
(and after drawing other elements) leads to full-screen flickering on Windows. It's as if the call toClear()
immediately clears the screen instead of deferring it toShow()
. The comment above illustrates this with a video. Here is the relevant code intview
. If I remove the call toClear()
, there is no flickering anymore (but this has other unintended side effects, so I would like to keepClear()
there).Is this the intended behaviour? If so, what's the best way to clear the screen buffer at the beginning of a drawing cycle?
The text was updated successfully, but these errors were encountered: