Gremlins uncovered that in a particular alert in my application, tapping
on the text of the message on a 3.5 debug ROM produces a "Invalid
insertion point position" fatal error. No error occurs on release
ROMs. This alert is relatively long (taking up about 2/3 of the
screen), but this is not the cause of the error as other longer alerts
have no problems. A single substitution is made using FrmCustomAlert;
the error occurs regardless of the length of the parameter text. What
could I be doing to cause this? Is it simply a case of the debug ROM
being too paranoid and checking the insertion point of a non-editable
field?
Thanks,
-Ben
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
