Re: CREATE WINDOW structured field (fwd)
James Rich <[email protected]> Tue, 13 Jul 2004 15:54:34 -0600 (MDT)
| Newsgroups | gmane.comp.java.tn5250j.devel |
|---|---|
| Message-ID | <[email protected]> |
Replying to just the tn5250j list since that seems like the best place for
everyone.
On Tue, 13 Jul 2004, Kenneth J. Pouncey wrote:
> Usually when a window is created there is a save screen issued and when
> a window is taken off the screen there is a restore screen issued. So
You say "usually". Is there any way to find out if this is always the
case?
> in reality you do not have to keep track of windows. What you have to
> do is save off the window(s) in the save screen and then recreate them
> on the restore screen. As you notice I do nothing with the clear gui
Hmm... In my case I think I want to keep track of them. If I can, that
will allow me to make the client much more flexible in terms of what it
can do.
> command yet. What I have seen with this is that you would clear all
> gui constucts from the screen in this command that was last created
> since the save screen. So some marker needs to be used. In my last
> version I am keeping the actual window structure that was passed so I
> can do this but have not fully implemented it (see below).
So far I've yet to ever receive the clear all gui constructs order. I
guess this only happens if there are gui elements other than windows
(scrollbars and the like perhaps?).
One of the ideas I had was to use a completely new buffer for the screen
everytime a save screen command was issued. Upon receiving the restore
screen destroy the new buffer and use the old one. This is how my demo of
x5250 worked for windows. Each window used it's own buffer. As windows
were created and destroyed so too were the respective buffers. That way a
marker is not required, just activate the previous buffer.
> I tried saving off the window structure a long time ago but the as400
> was not accepting all the data that I was sending so was not able to
> save off the window structure on a very busy screen so I just saved off
> the characters on the screen so when a restore screen is issued the
> window is not really recreated but just the characters on the screen
> were so the window gets restored like it would look by not using
> enhanced mode. This means that the characters :...............: get
> restored instead of the graphic symbols. I have since then redone the
> way I do a save screen and do not know if the window structure would be
> able to be saved off and restored without the as400 complaining. Also
> this was on a very old model of an as400 and also do not know if the
> controller has changed again.
Save the window structure - as part of the SAVE SCREEN command? For me,
the save screen command occurs before the create window structured field
occurs so there's no window to save. Unless you mean saving the window
structure that is sent to you as part of the create windows structured
field command, but that doesn't jibe with the rest of what you said.
Or do you mean when another window is created saving the first window as
part of the save screen command? In that case, I would have guessed that
you just save the contents of the window and not the sctructure or the
rest of the screen.
> There is a place in the document that explains how to compress the
> screen data but that did not work either, still too much data. So what
I wonder if this is because (if you are speaking of creating a second
window) it is only expecting the contents of the window, and not the whole
screen (or structure)?
You are clearly doing something smarter than me since you have functioning
windows and cursor progression working. I wonder if there is a way to
tell the as/400 that I support cursor progression but not the create
window structured field command?
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 sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com