On Mon, 10 Apr 2000, Mike Madore wrote:
> The first was the problem where hitting enter (or another aid generating
> key) two or more times in quick succession would cause an assertion
> complaining about trying to send fields when we weren't in a read state.
This appears to be fixed! Woohoo! (I've been looking for a fix to this
since the 0.13.x days)
> The other bug had to do with improper cursor placement (In DFU and some
> other programs). The cursor would always end up on the first non-bypass
> field regardless of where it was really supposed to go.
>
> This was due to improper handling of cursor placement in the
> write_to_display command. Our behavior was correct for a locked display
> (move to first non-bypass field). For an unlocked display, the behavior
> is to leave the cursor where it was. This seemed to be triggered in the
> case where we received two write_to_display commands in a row.
Hmm... this still needs work. DFU still positions the cursor to the
wrong line. Break messages still mess up the cursor placement.
Screens that use DSPATR(PC) in the DDS do appear to work now, which is
great!
>
> I would appreciate it if anyone who is able could check the code out of
> CVS and see if this fixes your problems. Also, if there are any new
> problems due to the fixes, I would like to know about them. I'll be
> fixing bugs all week.
>
End Key handling seems to have improved as well... Did someone work on
this, or is that just psychological? :)
+---
| This is the LINUX5250 Mailing List!
| To submit a new message, send your mail to [EMAIL PROTECTED]
| To subscribe to this list send email to [EMAIL PROTECTED]
| To unsubscribe from this list send email to [EMAIL PROTECTED]
| Questions should be directed to the list owner/operator: [EMAIL PROTECTED]
+---
