Re: [LINUX5250] incorrect cursor position

["KJ P" <kjpou@xxxxxxxxxxx>]

Mark

> Yes. My blood is boiling once again over this little cursor.
> I'll take a look at your code later (sf is down right now) and start
> getting back into the "IC/MC/WTD" state of mind and warm up ethereal.

Like I said the emulator code is not correct.  If you wan to start with your 
state machine go for it.  You will be one week ahead when I get back.

> If by enhanced you mean the "Write To Display: Structured Field Order" I'm
> not sure I agree with you %100 there.
No by enhanced mode I mean telling the controller that it is an enhanced 
terminal.  There are little bits in there that turn on and off each of these 
different options/functions for whether you support this and that.  Some I 
found only by looking at a CA trace.  Anyway we will discuss it when I get 
back.  If we can get it to work in the non enhanced mode then even better 
but never could get the correct sequence of IC and MC.  Three weeks was 
enough for me ;-)

Instead of clogging up this mailing list we can move it over to a personal 
one on one unless the people on this list are interested in this or the 
tn5250j-development list.  Either way is fine with me.  Was hoping to get 
the input from all of the tn5250 people as well.

Will be leaving at the end of the day so will catch your comments later.  
Hope all join in.

Regards

Kenneth

> From: MarkB@xxxxxxxxxx
> Reply-To: Linux 5250 Development Project <linux5250@xxxxxxxxxxxx>
> To: Linux 5250 Development Project <linux5250@xxxxxxxxxxxx>
> Subject: Re: [LINUX5250] incorrect cursor position
> Date: Wed, 21 May 2003 18:32:40 -0400
>
>
>
> >This is Kenneth from the tn5250j project.  I would be happy to talk shop
> >about the cursor positioning.  Well that is in about a week's time that 
> is
>
> >as tomorrow I will be leaving on vacation for a week and will not be back
> >until the beginning of June. ...
>
> Sounds good.
>
> >It is possible though to get it almost 100% even on restoring the windows
> >from savescreen and restorescreen functions.  The first thing that will
> have
> >to be done is get the enhanced functions turned on and working, then 
> there
>
> >is the exact flags in the query response back to the controller to return
> >the IC and MC commands in the correct order.
>
> If by enhanced you mean the "Write To Display: Structured Field Order" I'm
> not sure I agree with you %100 there.
> Correct me if I'm wrong, but don't we know if we pretend to be an older
> terminal in the Write Structured Field response, that the AS400 will never
> send WTD SFOs.
> These features can even be turned off in Client Access by editing your .ws
> session file. (I think it's something like ENPTUI=N (Enhanced
> Non-Programmable Terminal User Interface) in the [5250] section, but don't
> quote me on that.)
> Needless to say, _regardless_ of what type of terminal our emulators are
> emulating, the cursor should still end up in the right position.
>
> Back to what I said earlier about SaveScreen and RestoreScreen ignoring
> cursor position. It looks right now like I'm 100% wrong.
> The documentation actually says the exact opposite. I could have sworn that
> I had read that a RestoreScreen is always followed by a WTD to actually set
> the cursor position. But I can't seem to find where I read it.
>
> >Let me tell you it was almost
> >a solid three weeks flipping bits and options and then interpreting them.
>
> I believe it.
>
> >The tn5250j is still not correct until I sit down and start putting it
> into
> >there.
> >I hope this helps and again would be glad to talk to someone on this to
> get
> >another persons view.  What do you say?  You want to put this crusade
> >together and all three projects benefit?  Yes I know the code is a mess
> but
> >it has been progressing since the last time you looked at it.
>
> Yes. My blood is boiling once again over this little cursor.
> I'll take a look at your code later (sf is down right now) and start
> getting back into the "IC/MC/WTD" state of mind and warm up ethereal.
>
> I think what we could do to start is jointly create some sort of state
> diagram about behavior we know to be true, and behavior that is ambiguous
> in the documentation. Then we can we can begin to clarify exactly how many
> combinations of behavior we have to implement/test in order to cover all
> our bases with the ambiguous cases.
> This should also include any bit flags (WTD CCs, etc) we are suspicious of.
> We can then start to record what succeeds and fails with each test.
>
> -Mark
> email:
> markb
> cms400
> com
>
>
> _______________________________________________
> This is the Linux 5250 Development Project (LINUX5250) mailing list
> To post a message email: LINUX5250@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/linux5250
> or email: LINUX5250-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/linux5250.

_________________________________________________________________
STOP MORE SPAM with the new MSN 8 and get 2 months FREE*  
http://join.msn.com/?page=features/junkmail