> -----Original Message-----
> You shouldn't have to go through so much work to keep text from being
> selected in a non-editable field. Just catch the
> fldEnterEvent and return
> with handled = true. No need to mess with bounds checking,
> since the field
> already does this for you. If all the fields on the form are
> non-editable,
> then you don't even have to check which field is being entered.
Agreed, although, if you want to make the user's experience of tapping on an
uneditable field the same as tapping on a blank area of the form, you need
to handle the penDown. For example: If you have the insertion point in an
editable field, and then
you tap on an uneditable field, the insertion point will disappear, whereas
tapping on the background of the form will leave the insertion point in the
editable field. Handling the penDownEvent treats a user tap on an
uneditable field as though it was on a blank area of the form (ie: it acts
just as though you had called WinDrawChars instead of used a field).
Also . . .
Anyone else notice that the underlining of uneditable fields is different
from that of editable fields on 256 color modes, and 4-bit grey modes?
-DGA
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
