Scroll regions are lost after pause/resume

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Run an application that uses scroll regions
2. suspend application by going to a different activity
3. application updates the cursor / outputs chars to the screen (this is
easily demonstrated by using screen -x and attaching to an irc client like
bitchx)
4. return to connectbot

What is the expected output? What do you see instead?
the scroll regions are lost until they are redrawn.

What version of the product are you using? On what operating system?
r98

Original issue reported on code.google.com by not...@gmail.com on 31 Oct 2008 at 9:12

[GoogleCodeExporter]

Does it scroll in the wrong place or is it just not drawing part of the screen. 
I can
get it to not draw part of the screen, but I'm not sure what is causing this as 
of yet.

Original comment by kenny@the-b.org on 31 Oct 2008 at 5:50

• Changed state: Accepted

[GoogleCodeExporter]

it redraws the screen properly, but it just scrolls in the wrong place and the 
wrong
amount of lines.

In bitchx and other irc clients i've seen, all the future outputs to the screen 
will
only be in the top line of the two-line status bar.  they will overwrite each 
other
as well.  It's like the scroll region gets changed to 1 line and it just keeps
printing to the screen in the same place.

An easy way to reproduce is within bitchx.  Change activities for a bit with an 
IRC
client running (I've only tested this inside of screen as well).  When you 
resume
connectbot all the screen updates will be stuck in one place as described above.

Original comment by not...@gmail.com on 31 Oct 2008 at 5:55

[GoogleCodeExporter]

Okay, I'll try that. The makers of the de.mud.terminal package were apparently 
under
the mistaken impression that you couldn't move your cursor *in to* a scroll 
region,
so they wrote all this code to prevent that from happening. I thought I removed 
all
those mistakes, but maybe there is still some cruft leftover.

Original comment by kenny@the-b.org on 31 Oct 2008 at 7:29

[GoogleCodeExporter]

This is fixed in r122. We were resizing the buffer even when the size didn't 
change
which resets the scroll regions. Of course the other end wasn't redrawing since 
the
dimensions didn't change.

Original comment by kenny@the-b.org on 14 Nov 2008 at 8:13

• Changed state: Fixed

[GoogleCodeExporter]

Issue 88 has been merged into this issue.

Original comment by kenny@the-b.org on 27 Nov 2008 at 11:20