>Most of the day today I've been working on a bug that's found
>its way into our application. It a rather large application (500k+).
<SNIP>
>Upon further debugging I got into the assembly in the SelectDay()
>call and noticed that when crashing, it was making a call to
>FrmGetObjectIndex() with the _constant_ 10122
>I open Constructor (I'm doing all this in codewarrior) and look
>at my highest form ID. Yup, 10100, and I don't have a control
>in that form numbered10122.
>
>I changed that form's ID to 10200, and everything appears to be
>working. Evidently the Palm OS forces the use of ID 10100 for
>the Calendar form that it uses in the SelectDay() function.
>Are there any other "known" form ID's that shouldn't be used?
Not a new issue!
Simply, you shouldn't be using any ID's above 10000
Which means your 10200 form ID is a problem waiting to happen.
We also produce a very large application with many, many screens
and find this rule very restrictive.
Can Palm Source please formally define other ranges of IDs that
can be used by other programs outside of the 1 to 10000 range.
(note there are a couple of IDs you can't use even within this range,
see archives for details)
Can we use 33000 to 64000 ? This'd be a very good range
to use, if allowed.
Roger Stringer
Marietta Systems, Inc.
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/support/forums/
