The part concerning the Debug ROM was discussed on this forum earlier this
month. From Ken Krugler's 8/4/00 posting called "Re: Insertion point error in an
alert":

> Thanks for the app & debugging steps. The problem is that your alert
> message has a linefeed at the very end. The trailing linefeed is
> skipped when calculating the height of the message text, which is
> then used to resize the text field box in the alert. Unfortunately
> the insertion point is at the end of the text, so when you tap on the
> text, the field code correctly complains that the insertion point
> visible flag is set the field attributes, but the insertion point is
> on line 7 (the eighth line, since line counts are zero-based) which
> isn't visible, being below the bottom of the text field bounding
> rectangle.
>
> So the fix for you is to remove any trailing linefeeds from your
> alert messages. The fix for Palm OS is to trim off trailing linefeeds
> before creating the text field used in alerts. I'll put that on the
> list for future fixes.

I don't remember hearing before about the text scrolling away in Release ROMs.
Sounds interesting.

-- Keith Rollin
-- Palm OS Emulator engineer







"Rick Wagner" <[EMAIL PROTECTED]> on 08/24/2000 11:38:21 PM

Please respond to "Palm Developer Forum" <[EMAIL PROTECTED]>

Sent by:  "Rick Wagner" <[EMAIL PROTECTED]>


To:   "Palm Developer Forum" <[EMAIL PROTECTED]>
cc:    (Keith Rollin/US/PALM)
Subject:  Field.c, line 132 in FrmAlert(). Looks like bug in PalmOS...



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/

Reply via email to