RE: Full screen mode

I had just noticed the same problem the other day (I haven't used tn5250 in
a while).  It seems to happen more on a slower connection (I'm coming in
over the Internet instead of on the LAN).

Would you classify this fix as a kludge or a real fix?  (It does actually
solve the problem.)  I'm no C guru (I can barely read the language) but it
appears you're checking to see if the window is the size it's supposed to
be, and if not, waiting and checking again.  Is that essentially correct?
(What is the unit of measure for usleep?  microseconds?)

Thanks Scott!  I love the shift left and shift right too.  I didn't even
know CA could do that until someone mentioned it here.  My XTerm didn't
update from CVS, so I just added the two lines manually...

>-----Original Message-----
>From: Scott Klement
>Sent: Monday, September 03, 2001 2:06 PM
>To: linux5250@midrange.com
>Subject: Re: [LINUX5250] Full screen mode
>
>> Secondly I've tryed a screen in 27x132 mode and when go from a 80 to a
>> 132 screen, the size of the screen change immediately but the part of
>> the screen between 80th and 132th row stay black until I press "page
>> down" or "page up" button. Will this bug fix in the next version ?
>
>I've done some looking into this issue, and it appears that for some
>reason the width of the screen according to curses doesn't update
>immediately.
>
>Here's an experimental patch you can try to see if it solves that problem
>for you...
>
>--- cursesterm.c        2001/09/03 08:06:53     1.35
>+++ cursesterm.c        2001/09/03 18:00:49
>@@ -616,6 +616,12 @@
>       }
>       This->data->last_width = tn5250_display_width(display);
>       This->data->last_height = tn5250_display_height(display);
>+      for (x=0; x<10; x++) {
>+          refresh ();
>+          if
>(tn5250_display_width(display)==curses_terminal_width(This)-1)
>+              break;
>+          usleep(10000);
>+      }
>    }
>    attrset(A_NORMAL);
>    getmaxyx(stdscr, my, mx);
>