Events posted to your app's main event loop can be seen by something like:
if ( !PreprocessEvent( &event ) ) {
if ( !SysHandleEvent( &event ) ) {
if ( !MenuHandleEvent( NULL, &event, &error ) ) {
if ( !ApplicationHandleEvent( &event ) ) {
FrmDispatchEvent( &event );
}
}
}
}
this inserts a custom function of your own to preprocess any events you
want.
You can then easily set a breakpoint here after doing an API call of
interest.
This same approach works for other event loops (if you have them).
Regards,
Randy Maxwell
-----Original Message-----
From: Richard Hartman [mailto:[EMAIL PROTECTED]]
Sent: Friday, March 10, 2000 5:20 PM
To: Palm Developer Forum
Subject: Events vs. API functions
I'm still trying to get a handle on what events can be considered to be
triggered by which API functions. For example, a FrmGotoForm() will result
(I -think-) in a frmLoadEvent followed by frmOpenEvent. Otoh, a
FrmDoDialog() will -not- trigger in a frmOpenEvent. Where can I find out
the cause(es) (API calls) that trigger the various events, and/or the events
triggered by each API call?
--
-Richard M. Hartman
[EMAIL PROTECTED]
186,000 mi/sec: not just a good idea, it's the LAW!
--
For information on using the Palm Developer Forums, or to unsubscribe,
please see http://www.palm.com/devzone/mailinglists.html
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palm.com/devzone/mailinglists.html
