----- Original Message -----
From: "Dr. Vesselin Bontchev" <[EMAIL PROTECTED]>
> > Register for sysNotifyDBCreatedEvent notification.
>
> Ah! That would solve the problem, indeed, thanks! I'll just have to find a
way to pass the information that a database has been created from the
notification handler to the code that's looping through the databases - so
that it knows it must abort. OK, I can probably do that with feature
memory...
>
> But wait - this notification is available only in PalmOS 5.x. What about
the earlier versions?
I don't know. From the commercial point of view (if you are going to sell
the app), the OS4 users represent only a negligible fraction of the
potential users.
> > Yes, but I would consider it safe only for a fg application.
> > Imagine an app that performs a modal event loop as part of
> > processing of the dialog button press. (I.e. called from the
> > form handler of the active dialog.)
> > Assume further that the active form did not change.
> > In this scenario the bkg application cannot do what you suggest.
>
> But can that actually happen? When I start the scanning of multiple
databases or files from a HotSync or card insertion event, I'll show my own
user interface (progress bar or current path or whatever). I'll have my
current form - I need that, in order to allow the user to abort the process.
If the foreground application doesn't let me do that (e.g., because it's
polling a control in a loop), then it won't let me work at all (or anybody
else, for that matter).
>
> Or have I misunderstood what you wrote above?
If you are in control of the UI, then you can afford to do it. Otherwise
probably not. I should have used this terminology instead of using fg/bkg
applications.
Best regards,
Jan Slodicka
--
For information on using the Palm Developer Forums, or to unsubscribe, please
see http://www.palmos.com/dev/support/forums/
