-
-
Notifications
You must be signed in to change notification settings - Fork 121
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
scrolling planes ought scroll up their bound planes #1883
Comments
note that the rendering engine will need to know about screen scrolling, or else it's going to redraw a bunch of stuff (the entire screen, effectively, since it'll think everything's one line off), massively hurting performance. |
good news, everyone! i figured it all out while on a walk. i'll write it up in a bit, gotta hop for work. |
#1853 describes my plans, RFC |
be sure we observe |
ok, so what happens when we scroll a bound plane partially or entirely off the plane to which it is bound? i'm inclined to think it ought work "like the real world" -- the subplane would scroll up until it is entirely distinct from the supraplane, at which point further scrolling would no longer move it. essentially, the rule becomes "when a plane is scrolling, subplanes intersecting it scroll along with it." i think that's reasonable. we do not destroy the plane once it's scrolled off or anything -- that's still up to the user. properly doing this will require the ability to draw partial bitmaps. this need is evident even in |
very promising: the first attempt does indeed fix |
YAY the logo is now always correctly placed!!!! |
hrmm we can get this |
If a plane is scrolling, and it has subplanes, those subplanes ought scroll along with it. This is particularly important for the scrolling-standard-plane case. Right now, this is necessary to properly draw a sprixel in
notcurses-info
that scrolls up with the other output, and proving out this concept is central to the whole idea.The text was updated successfully, but these errors were encountered: