At 12:00am -0700 00-09-26, Palm Developer Forum digest wrote:
>Subject: RE: Bad Field Selection - Line: 5321
>From: Chris DiPierro <[EMAIL PROTECTED]>
>Date: Mon, 25 Sep 2000 10:20:56 -0400 (EDT)
>X-Message-Number: 46
>
>This seems related to the popup keyboard (like the February discussion
>that never got resolved). Can Palm comment on this one?
The bug discussed in February turned out to be operator error. From
the developer:
>From memory, what
>happened was that I was updating a field (in response to a frmUpdateEvent)
>and the selection got out of sync with that current in the keyboard dialog.
>The fix was to remove the frmUpdateEvent processing for the field. (At the
>time, I had this idea of centralising all display updates in frmUpdateEvent
>with corresponding FrmUpdateForm calls.)
And from Ben Combee...
> > Subject: Re: Bad Field Selection - Line: 5321
> > From: "Ben Combee" <[EMAIL PROTECTED]>
> > Date: Thu, 21 Sep 2000 17:25:12 -0500
> > X-Message-Number: 54
> >
> > There is a known bug in the PalmOS field editing code with up/down
> > keystrokes and deleting selections -- it was discussed here a couple of
> > months ago. Maybe you're hitting that.
From what I recall, the bug(s) related to up/down arrow key handling
didn't cause a "Bad Field Selection" fatal alert, just odd editing
behavior.
-- Ken
Ken Krugler
TransPac Software, Inc.
<http://www.transpac.com>
+1 530-470-9200
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
