-
Notifications
You must be signed in to change notification settings - Fork 814
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
Revised progress bar ETA #4054
Comments
As suggested in Textualize#4054
While making a start on this I ran into some confusing results and ended up uncovering #4096; so I think this will result in a revamp of how Some form of "please reset this |
WiP on this has addressed #4096, but also uncovered a further issue where the An updated method of calculating the ETA is now in place and seems to produce reasonable results; for constant-time progress the timer looks spot on; and for accelerating, decelerating and reasonably random progress the results look good too, and generally more/less optimistic/pessimistic where appropriate. Work on this is having further knock-on effects on how the documentation screen shots are generated, and also their use in snapshot tests; this will likely need some more work on how the docs for A question has also been raised about the newer approach taken to slide a window over the updates to perform the calculation. +1d |
Don't forget to star the repository! Follow @textualizeio for Textual updates. |
The ProgressBar "ETA" is quite naive. I think it assumes a constant speed, which is rarely the case for things you would want a progress bar for.
We need a smarter way of calculating the ETA which emphasizes more recent data points. There are a few ways of doing this. You could see the Rich progress bars for an examples, but there may also be better algorithms. Suggesting asking Google or ChatGPT.
The implementation could also use another look. It adds a Horizontal container, where the widget itself could have a horizontal layout.
1d
The text was updated successfully, but these errors were encountered: