Re: tn5250-0.15.2 is realeased.

On Mon, Nov 22, 1999 at 02:49:50PM -0500, Sean Porterfield wrote:
> 
> Assertion (This)->cx < (This)->w failed at dbuffer.c, line 115.
> 
> Trace file attached for this one :)

Okay, I've filed it away and will check next chance I get.

> 
> > >
> > > > > I can't enter anything in my numeric field anymore and was going to 
>look
> > > > > up what data type it was.  It has an S for keyboard shift of Signed
> > > > > Numeric.
> > > >
> > > > Fixed.
> > >
> > > Not on mine!  :)  The whole session locked up on that one and still 
>doesn't allow
> > > anything in the Y data type.
> >
> > Uh, my fixing actually broke more than it fixed ;)  The fix was fixed and 
>the
> > fix fix is now in CVS ;)  I'm not making a release just yet because I'm 
>having
> > a problem during testing and I'm not sure if it has to do with the emulator
> > or my horrific first attempts at AS/400 CL.  The scoop is that the fields 
>may
> > be transmitting to the 400 improperly, but entering data in Numeric Only and
> > Signed Numeric fields should be completely to spec now, including fully 
>proper
> > Field Exit/ Field- / Field+ handling.
> 
> After I stopped laughing from your explanation (I can relate to fixing a fix) 
>I tested
> my numeric fields and they worked as I expected (converting a 1- to a J and 
>so forth)
> as well as field+ making it positive again.  Good job!

... except that it _wasn't_ transmitting all the numeric fields properly as I
had suspected.  *That* is now in CVS, and that bug should be titled 'Negative
Signed Numeric Fields Cause AS/400 to Puke'.  On the brighter side, because 
I've fixed serious bugs with all possible aspects of how the emulator should
handle numeric data, I can now guaruntee that it's numeric data handling is
perfectly stable ;)

So my CL isn't all that bad.  (Actually, it's like three lines ;)  "Program
Checks" scare me.  It's like a core dump with a lot more words and somewhat
less information.

> 
> One other thing that's been there for a while but bothers me a bit: if you 
>type ahead
> of the screen update, it does remember what you type, but it does not display 
>until
> you type something after that screen has displayed.

Hmm, I'll check this out, but it doesn't make much sense, since the screen is
updated after every keystroke.  Actually, the flickering problem has to do
with the screen being updated *too* often (sometimes three times per key).

> 
> Thanks for your quick response, hope the trace file helps some (it's the 132 
>character
> screen crash).


-Jay 'Eraserhead' Felice
+---
| This is the LINUX5250 Mailing List!
| To submit a new message, send your mail to LINUX5250@midrange.com.
| To subscribe to this list send email to LINUX5250-SUB@midrange.com.
| To unsubscribe from this list send email to LINUX5250-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---