-
Notifications
You must be signed in to change notification settings - Fork 96
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
Graph characters not clearing on row change (asciichartpy)? #50
Comments
(ignore the colors, that's just an artifact of my HDMI capture device; it's all one color on-screen) |
Opened PR #51 for this |
@DoktorJ thank you! Will check and merge shortly! |
@DoktorJ can you plz post the code you use to reproduce the above graph? Namely, the instantiation/configuration code and the series. It might be caused by a different issue (not related to rstrip(), possibly an encoding issue or something related). |
@DoktorJ also, it would help if you could post your result of |
@kroitor it's part of a bash loop that monitors system temperature. First the configuration is set up outside the loop, based on detected display parameters to try to maximize graph size and keep the Y-axis intervals clean, instead of weirdly-rounded decimal numbers...
and then the loop itself does this:
I pulled my specific PR and ran test.py, then switched back to master and ran again, also checked the return value just for shiggles:
|
BTW it may not be immediately apparent on the |
I didn't seem to have this problem with a previous version, but since dropping in 1.5.12 (thank you for reimplementing the user specification of characters!), I've got this issue where the graph doesn't clear adjacent rows when it shifts; see screenshot.
When the graph is at its max width and redrawing over a previous graph, it no longer clears these characters when scrolling. I looked at the commit history, and determined this bug is caused by commit e9adb0d, with the addition of the
.rstrip()
call; when I edited my init.py and removed.rstrip()
the graph behaves as it used to.The text was updated successfully, but these errors were encountered: