-
Notifications
You must be signed in to change notification settings - Fork 765
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
Reduce blanking effect? #25
Comments
I'm thinking this is out of your hands because that's how gdb does things? But, I think I can use DASHBOARD_TTY as a workaround... that doesn't seem to exhibit the issue since it doesn't share printing with gdb. |
I can confirm that using DASHBOARD_TTY is massively faster. Not only is the blanking practically non-existent, updates are way faster in general. |
Yeah, this is annoying, I know, and your reasoning is sound. The time needed to build the dashboard is perceived as a blank terminal as the screen needs to be cleared in order to have the dashboard in the same place at the next step. Unfortunately I cannot buffer the content because (to my knowledge) there's no way to fetch the normal GDB output (e.g.,
Note that I cannot build the dashboard at step 1 an the program status has not evolved yet. Now one could think to completely ignore that run-time information, but since it is not limited to breakpoints notification I'm not sure it's a good idea. Moreover, there's the program I/O which cannot be ignored.
In that case it should not be blanking at all since as the dashboard can be buffered and the behavior is similar to the one you're suggesting. Talking about solutions I can only think about to:
I'll leave the issue open as I'd like to improve this aspect. Thanks for reporting. |
I finally managed to look into this, now the blanking effect should be drastically reduced, at least for what concerns the assembly module. |
Do you think it would be possible to reduce the amount of time that the terminal becomes blank between the updates?
i.e. Does it currently happen like this?
OnUpdate:
Clear Terminal
Gather / Print results
And if so, could it work more like this?
OnUpdate:
Gather / Buffer results
Clear terminal
Print buffered results
My reasoning:
The blanking causes me to lose my place visually. For example, if I'm trying to keep my eye on a particular watch expression, and I "next" (which triggers an update), The terminal blanks for probably a good 500-800 milliseconds before being redrawn, which causes me to lose my place...
The text was updated successfully, but these errors were encountered: