Re: RE: Question for xt5250

Neither could I when I tried it yesterday, and the RPMFIND site has
shutdown due to "software patents".

Joel


On Fri, 2003-08-29 at 08:15, Sean Porterfield wrote:
> > Sean Porterfield wrote:
> > 
> >>The "tn5250_display_do_aidkey (0x34) called." (which I'm hoping is F4)
> >>is before the splash screen in the log file.
> >>
> >>Somehow Client Access knows you can't press any keys on that screen and
> >>keeps the keys buffered until the next screen is displayed.
> 
> Scott Klement wrote:
>  > Is this something that broke when I implemented the various keyboard
>  > states back in Nov 2002?   Does version 0.16.5 work?  It was released
>  > prior to that change.
> 
> I couldn't get 0.16.5 to compile on RH9 (I haven't looked into the 
> problem yet, I'm likely missing something) but I tried it at home last 
> night and got the same result.
> 
> One thing - a long time ago I had keyboard buffering problems that were 
> fixed later (and are still fixed.)  This issue is apparently different 
> somehow.  That means I can't tell when it "broke" because it may never 
> have worked.  I wasn't using OMS/400 or DBU during that time frame.
> 
> I'll see if I can create a program that reproduces the error.
> 
> _______________________________________________
> 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.