I brlieve that you can access objects in the form and change things as long
as you are careful not to call any of the functions which actually acuse
that element to be drawn. If you actuall draw the element to the screen
before the form is draw and the 'save behind' property is on for the form,
the information you have just drawn will be capture as part of the form
'behind' this one and will be resored if you do a FrmGotoForm(0) to exit the
form
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Howard
C. Shaw III
Sent: Monday, July 03, 2000 14:21
To: Palm Developer Forum
Subject: FrmDrawForm before form access
Palm OS 3.0 to 3.5 at least, all allow access to form elements before the
form is drawn. Palm documentation says this is not allowable, and the debug
roms fail if you do it.
But I, for one, would very much prefer the current state of affairs to be
recognized by Palm and documented as an allowed usage.
Basically, with standard form elements, it provides a sort of
double-buffering, in that you can make your changes to the not-yet-onscreen
form, then draw the complete form, in its final edited stage.
When using this illegal technique, forms pop-up already filled out, without
the unpleasant flickering as various pieces are hidden and shown, or
redrawn, etc.
Is there any other way of achieving this admirable result, other than
defying Palm's documentation and risking future code failure?
What are the particular dangers to this approach, and why shouldn't it be
supported?
Howard C. Shaw III
Programmer
Tyrol Data Systems
--
For information on using the Palm Developer Forums, or to unsubscribe,
please see http://www.palmos.com/dev/tech/support/forums/
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
