|
"Jason M. Felice" wrote: > There are updates in CVS. > > On Mon, Nov 22, 1999 at 09:06:27AM -0500, Sean Porterfield wrote: > > > > I saw some strange colors and data flash up on my screen then disappear. > > > > > > Fixed, I think. > > > > Different, but still there. My whole screen turned blue with tiny >horizontal > > black lines (like they were blue cursors and the black was space between >lines.) > > There were some other colors and symbols, but it flashes off too fast to >really > > see. > > Hmm, I caught a very strange issue where random keystrokes would be 'handled' > for no apparent reason when the emulator first starts up - I've added a work- > around, but I should really address this and figure out why later. On my > machine, it puts some strange escape characters into the display and causes > the first few fields of the signon to turn inverse purple. This may or may > not be the same issue. Just got the latest from CVS and can't produce this again > > > When I tried to browse a source member in SEU, it crashed: > > > > Assertion (This)->cx < (This)->w failed at dbuffer.c, line 114. > > > > > > Hmmm, try it out. I don't think so, but... > > > > Still crashes, haven't checked for a specific error. > > Hmm, I've done this a few times but don't seem to have any problems. If >you're > still getting this, send me a trace file. Assertion (This)->cx < (This)->w failed at dbuffer.c, line 115. Trace file attached for this one :) > > > > > > 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! > > It screws up even if I don't key in any field - just go in then F3 back >out. My > > screen has all the text in the first few lines, then a purple patch, then a >lot > > of red lines. Very odd! > > > > If that makes any sense at all... Would a trace file help, or perhaps are >you > > aware of this already? > > Yes, I am already aware of the fact that a trace file would help ;) Well, you must have fixed this; I can't make it do it anymore. That's a good thing though. (If you keep answering like this, people are going to think I'm having too much fun at work.) 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. Thanks for your quick response, hope the trace file helps some (it's the 132 character screen crash).
As an Amazon Associate we earn from qualifying purchases.
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.