David Fedor wrote:
> >But amazingly, it is documented - but it's one of those explanations that
> >you only tend to find when you read the docs cover to cover...
>
> Or if you read the "top issues when going to 3.5" page at
> http://www.palmos.com/dev/tech/docs/palmos35/topissues.html
>
> You might want to read the rest of the stuff there too :-)
>
Ouch! :)
Guess I have to keep on top of checking for documentation updates.
Thanks the tip, David.
For those like me who didn't know, the "top issues" page now looks like a knowledge
base printout of bug reports. Reading this one
"cover to cover" was a challenge, but by searching on the page for "bus error", I
found the relevant entry:
Problem Symptom:
Application crashes while drawing, particularly
either right on startup or when
switching to a new form
Problem Cause:
If there isn't yet a valid window created or
designated as active, drawing routines on
a debug rom will generate a bus error. This is to
help developers find situations in
which they are drawing in the wrong context, or
unnecessarily.
Solution:
Don't draw to a form until FrmDrawForm has been
called to draw the form's
background and establish it as the active form.
Additional Info:
On a release rom, if there is no active window,
drawing will draw right on the main
(root) window. This will often have the intended
result, but not necessarily. Fixing
the application to target the drawing properly is
usually the right thing to do.
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
