-
Notifications
You must be signed in to change notification settings - Fork 5
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
ui can get screwed up when switching contexts #3
Comments
Trashed the 75% thing and did some math magic to keep messages from overflowing and causing the weird Diffy glitch. I don't think Diffy cares about what's off the top of the screen and that's what was screwing up the UI. 196f029 |
@stripedpajamas hey did your math magic fix the ui glitches you were seeing? i'm having similar issues with cabal :) |
hi @cblgh :) yeah the math magic fixed it! or at least it was a better work around. it seemed like the glitch was whenever i had too much content to fit on one terminal screen, diffy would kind of not work very well. i couldn't ever figure out how to make diffy play nice, so i ended up determining how many lines the chat messages (including word wraps when applicable) would take up, and then filtering my message list to only show x number of messages -- so my content always fits on one terminal screen. and then to allow scrolling up into previous messages, i added listeners to page-up/page-down to move the message view-- but never showing more than a terminal screen can handle. and that kept diffy v happy. |
@stripedpajamas thanks for the response! i'll see if we can find the right mathemagic to fix this in cabal (or even fix it upstream in diffy... hmmmmm) |
there seems to be an issue with diffy when the messages array gets drastically filtered (switching between public and private contexts). I filed an issue with mafintosh and in the meantime tried to workaround by having scat only fill up ~75% of the screen, but i'm not sure if the workaround is working around too well.
The text was updated successfully, but these errors were encountered: