I'm not sure if this is classified as a bug or "undefinied behavior". To replicate: Create an alert in constructor, put whatever title you want and whatever message you want. BUT, at the end of the message put an extra carriage return or two (like you wanted to make the alert pretty). Now build your app, run it, and call your alert (with FrmAlert() of course). In the alert dialog box, tap anywhere on the message text and it chokes. Debug Rom Results (3.5 tested): Here you get the Field.c, line:132 error followed by a couple of others. Stack trace shows it happening deep inside FrmAlert(). Release Rom Results (2.0,3.5 tested): By dragging my pen over the alert you can make the alert text disappear. What looks like is actually happening is that PalmOS is scrolling the field within the Alert dialog. That's all. Killed a solid hour tracking the Gremlins error down. Especially since it was just after I had finished a module where was dinking around with insertion points. -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/tech/support/forums/
