RE: Screen bleeding

In fact, I can send you the sources, but I had troubles making a diff file; 
it's a reason why some of my changes never got into tn5250. I'll learn to use 
the GNU tools someday. Some of my changes are relatively generic, like removing 
all the static variables in function so it works in a multithreaded 
application. I made many globals const, since they were const. :) It's all 
about being able to use 2 terminals in one app without crashing.

But I have an idea about what could do the problem, I activated the enhanced 
terminal in the protocol so the "continued fields" could be supported (I did 
something that make it works) but I never supported windows and all the other 
enhanced terminal functionalities so it could be those things that screw the 
screen.

Mail me privately for the latest sources, I lost my web site and never took the 
time (and money) to make a new one.
I will try to make a working diff file. Probably next week I'll reinstall the 
CVS software.

Marc-Antoine Ruel

> -----Message d'origine-----
> DeÂ: linux5250-bounces@xxxxxxxxxxxx [mailto:linux5250-
> bounces@xxxxxxxxxxxx] De la part de James Rich
> EnvoyÃÂ: 4 fÃvrier, 2005 15:27
> ÃÂ: Linux 5250 Development Project
> ObjetÂ: Re: [LINUX5250] Screen bleeding
> 
> On Fri, 4 Feb 2005, Ruel, Marc-Antoine wrote:
> 
> > I heard one user telling me that he got "screen bleeding" when changing
> > of pages; some letters of the previous page stays on the screen.
> >
> > I still haven't reproduced the problem; I'll try it in near future; the
> > user is at a remote site.
> >
> > I just wanted to know if anyone got this type of problem.
> >
> > I'm using the HEAD branch with custom modification. So, yes, I'll look
> > into my modifications first :)
> 
> This is using just tn5250 (or xt5250), not x5250 right?  x5250 had this
> problem but it has since been fixed.  That's the only case I've heard of
> such problems.  tn5250 has always been flawless.
> 
> Can you show us the mods?
> 
> James Rich
> 
> It's not the software that's free; it's you.
>       - billyskank on Groklaw