Re: RE: Question for xt5250 -- LINUX5250

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: Re: [LINUX5250] RE: Question for xt5250
From: Scott Klement <klemscot@xxxxxxxxxxxx>
Date: Thu, 28 Aug 2003 15:46:59 -0500 (CDT)
List-archive: <http://archive.midrange.com/linux5250>
List-help: <mailto:linux5250-request@midrange.com?subject=help>
List-id: Linux 5250 Development Project <linux5250.midrange.com>
List-post: <mailto:linux5250@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/linux5250>, <mailto:linux5250-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/linux5250>, <mailto:linux5250-request@midrange.com?subject=unsubscribe>

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.

On Thu, 28 Aug 2003, 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.
>

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: RE: Question for xt5250 , Sean Porterfield

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.