That sounds about like how I'm doing it - the application has the whole screen to write, but if it only uses the top, the terminal wrapper doesn't touch everything below.
You may have gotten as far as I have - I haven't done a ton of testing with different terminals. I don't recall having trouble with writing a full line at the bottom, but I think I never write newlines - I just go to the next line and keep writing. I sent the first email to the list, but it was 11 months ago :) Perhaps I hadn't signed up for the list yet? I probably sent it right after signing up. Tom On Sat, May 10, 2014 at 3:33 PM, Ian Ward <[email protected]> wrote: > On Sat, May 10, 2014 at 8:34 AM, Ian Ward <[email protected]> wrote: > > Absolutely > > > > I started work in this direction with raw_display but never quite > finished. > > In particular, the way I started to implement this feature was to have > the user set alternate_buffer=False when raw_display.Screen.start() > and then when the application didn't draw on the lower portion of the > screen (left it as blank space with the default display attributes) > then that many rows of the original screen would be left intact above > where the urwid application was drawing. > > I ran into trouble with the way different terminals handled > positioning the cursor after a newline. I couldn't use absolute > positioning any more because I didn't know if the screen had scrolled. > I'm interested to look at your solution. > > I also wonder why I missed your first email. Was it sent to this list? > > Ian > > _______________________________________________ > Urwid mailing list > [email protected] > http://lists.excess.org/mailman/listinfo/urwid >
_______________________________________________ Urwid mailing list [email protected] http://lists.excess.org/mailman/listinfo/urwid
