Re: Re: [LINUX5250] SAVE SCREEN and RESTORE SCREEN commands

Hello James and Scott

Hope the weekend is going ok for you guys.

Scott is correct here and explained it a lot better than I did.  I just 
use the save screen as a repository of anything I want sent back to me 
including the structures.  Am not sure about the whys and where of it 
so memory could have been a factor and makes sense.  I used to use my 
own buffers at first but after 5 screens or windows down my PC with the 
jvm and swing was eating up memory with 8 - 10 sessions open.

Like I said before I had problems with the size of the stream I was 
sending back when in enhanced mode.  It could be the way the stream was 
being sent back though and almost sure of it.  I might have to take a 
look at the wtd.c code to see how it is doing the streams.

I hope that works for you because it would definately be better than 
what I did so please let me know.  Will be taking a look at this again 
in the future but need to get the headless code in the project.  If all 
works correctly the painting code will be a hell of a lot faster and 
even over a DSL connection get almost instant screen updates now in the 
beta version of the terminal code.  Crossing my fingers because my 
painting code sucks and really needed updating/rewriting.

Have a good weekend

Regards

Kenneth





On Jul 16, 2004, at 10:13 PM, James Rich wrote:

> On Fri, 16 Jul 2004, Scott Klement wrote:
>
>>> When a SAVE SCREEN is issued, who does the saving?  The 5250 client, 
>>> or
>>
>> When the AS/400 sends us a SAVE SCREEN operation, all of the data 
>> that we
>> have for the screen is sent back to the AS/400.  The AS/400 saves that
>> data somewhere.
>>
>> Then, when a RESTORE SCREEN is issued, it's followed by the data that 
>> we
>> sent it, allowing us to completely restore the screen to back to what 
>> it
>> was.
>
> Ok, great.  That clears up some confusion.
>
>> The way that lib5250 implements this process is that it generates an
>> actual 5250 data stream that can be used to reproduce the screen.  
>> That
>> data is sent to the AS/400 in response to SAVE SCREEN.  When the 
>> RESTORE
>> SCREEN is issued, that same 5250 data stream is sent back to us, and 
>> we
>> interpret it like any other 5250 data stream that we receive.
>
> Ok, that explains wtd.c.
>
>>> Are GUI elements (such as scrollbars) sent as part of the SAVE SCREEN
>>> command?  The docs don't really say that I can tell.  What about 
>>> windows?
>>
>> Are you asking if they ARE, or if they SHOULD BE?!  I don't know if 
>> they
>
> Should be.  From the rest of your message it looks like the spec is to
> send all GUI components back to the AS/400 as well.
>
>> I suspect that the problem is that when you added the window code to
>> lib5250, you did not add it to wtd.c, so that it doesn't get sent in
>> response to SAVE SCREEN -- and therefore doesn't get sent back in 
>> response
>> to RESTORE SCREEN.
>
> You are right.  I'll have a look at wtd.c and see about adding in the
> appropriate stuff to get the GUI components back on a RESTORE SCREEN.
> I'll think that's all I need to get windows working correctly in 
> enhanced
> mode.  Scrollbars too :)
>
>> I don't know how else to explain it.
>
> You explained it perfectly.  Thanks!
>
> James Rich
>
> Vs lbh cynl n Zvpebfsg PQ  onpxjneqf, lbh pna urne fngnavp zrffntrf. 
> Ohg
> rira jbefr, vs lbh cynl vg sbejneq, vg vafgnyyf gurve fbsgjner!
>         -- Fcbgvphf ba /.
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by BEA Weblogic Workshop
> FREE Java Enterprise J2EE developer tools!
> Get your free copy of BEA WebLogic Workshop 8.1 today.
> http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
> _______________________________________________
> Tn5250j-develop mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/tn5250j-develop
>



-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click