FrmDrawForm seems to behave differently in 3.2 (Palm VII) than before:
it erases the form before drawing the objects. In 3.1 and earlier, it
doesn't erase what's already on screen, and in fact my code is taking
advantage of that fact. So now it's erasing parts of my interface!
Several of my frmOpen event handlers look like this:
{
Draw_Special_Gadget_1();
Draw_Special_Gadget_2();
FrmDrawForm( FrmGetActiveForm()); // draw everything else
}
This works fine through 3.1, but in 3.2 the FrmDrawForm call erases the
two gadgets that were just drawn by the previous lines. Not good! Is
this a bug introduced in 3.2 or an intended behavior change?
This is definitely not mentioned in the preliminary 3.1/3.2 SDK
documentation, where FrmDrawForm is the same for both versions.
(Yes, don't tell me, obviously the "fix" is to rearrange the draw calls
to call FrmDrawForm first, but my point here is to complain about this
subtle behavior change which could break existing applications.)
-slj-
