× 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.



It crashed because I didn't initialize my instance the same way (i.e. no 0 
default initialization). Anyway it's fixed (here).

To reduce the overhead of redrawing, I putted a 10 ms delay before redrawing 
when I get a new character, which is reset at each new character. A user 
wouldn't notice the delay and it fixed the "overload" problem easily.

But that is still a good idea that you had.

Marc-Antoine Ruel
 

> -----Message d'origine-----
> De : linux5250-bounces@xxxxxxxxxxxx 
> [mailto:linux5250-bounces@xxxxxxxxxxxx] De la part de James Rich
> Envoyé : 5 mai, 2005 17:01
> À : Linux 5250 Development Project
> Objet : RE: [LINUX5250] tn5250 0.17.3 released
> 
> On Thu, 5 May 2005, Ruel, Marc-Antoine wrote:
> 
> > I just tested A5250 and it crashed at first key press in 
> > tn5250_terminal_putkey(). I'll debug it right now. For the 
> win32 port, 
> > beside starting it and logging into the server, I haven't 
> tried it much.
> > Anyway the enhanced protocol (windows and menus) aren't 
> implemented in 
> > the win32/a5250 ports.
> 
> I initialized the other terminals to put NULL for that 
> function.  You don't really need to use it and lib5250 does 
> properly check if it is NULL. 
> It is useful to allow lib5250 to draw individual keystrokes 
> without requiring a call to the update() function (which 
> redraws the whole screen).  It is useful for showing 
> keystrokes resulting from macros and typeahead.
> 
> James Rich



As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.