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
[BUG] Addressing Dashboard Freeze and Cursor Flicker Issues in Real-Time Data Applications Using Rich #3264
Comments
Can you provide a MRE to reproduce the issue you're describing? |
I deleted all what is not needed ... but it shows the issue. If I ran tis code on windows 2022 Server it freaks out...
|
Screen.Recording.2024-01-25.at.02.11.59.mov |
Here you see the freeze of UI Screen.Recording.2024-01-25.at.02.15.01.mov |
I get the same pause effect with a Windows console window if I run this program, no Rich involved at all: from time import sleep
for n in range(10_000):
print(str(n))
sleep(1) This seems to be standard behaviour for Windows console and nothing to do with Rich. I'm no Windows person, but a quick search online suggests this is related to something called "Quick Edit Mode", perhaps? |
You may want to try the new Windows Terminal. The legacy terminal has a lot of issues. You also may want to consider the Textual for things like this. |
Hi, best |
Will is suggesting that you look at Windows Terminal. |
Thanks, i will give it a try. However i can not guarantee that this new styled terminal is installed on the clients machine. looks like there is a github repository enabling download |
Hi,
I have created a dashboard with real-time data using Rich. However, I am encountering two issues. First, the input cursor from the terminal occasionally flickers, which leads people to click on the UI, causing it to freeze until I resize the terminal window. Second, it appears that when the UI freezes due to mouse clicks, some of my backend processes, like logging to files, also start to freeze.
python == 3.11
rich==13.7.0
Running on Windows 11 and Windows Server 2022.
The text was updated successfully, but these errors were encountered: