At 12:54 PM -0800 2/7/07, Lionscribe wrote:
I do it all the time for short computations. The functions
FrmInitForm, FrmDrawForm,
FrmEraseForm, FrmDeleteForm
do not cause events.
My uncertainty is whether they are at the mercy of events--that is,
if another app generates an event, can those calls be intercepted?
But in long computations it is only fair to let user cancel in
middle, especially on a Treo where a Phone Call may be coming in.
Either use a separate event loop, or keep on posting custom events
and do part of the computation by each event.
I agree with that in general. But I think there is a case to be made
for exceptions.
I got the sense from OP that this computation is rarely performed.
So I think it's fair to warn the user they won't be able to abort,
and then just dive in and get it done. The overhead of providing an
abort in the middle of the process isn't worth the engineering time.
Or maybe it is--but this is a design/business decision, not a
dogmatic one.
--
Hal Mueller [EMAIL PROTECTED]
Mobile Geographics LLC http://www.mobilegeographics.com/
--
For information on using the PalmSource Developer Forums, or to unsubscribe,
please see http://www.palmos.com/dev/support/forums/
