You need to make sure your registered functions don't move around on you, because the OS will not automatically adjust them. You do this by opening the application database (and overlays, as necessary) and locking the resources. The OS does this for you when you run your app, but unlocks and closes the app when you exit. You need to do it in addition to the OS, so that when the OS unlocks and closes, you still have them open and locked.
-------------------- Jeff Loucks Work 425-284-1128 [EMAIL PROTECTED] Home 253-851-8908 [EMAIL PROTECTED] Mobile 253-691-8812 -----Original Message----- From: Rob [mailto:[EMAIL PROTECTED] Sent: Thursday, February 24, 2005 2:42 PM To: Palm Developer Forum Subject: Are notifications pointing to functions bad? My application (Butler) is crashing in two scenarios 1) After I run flyzip's stability test (at the end immediately after the defrag) 2) After some hotsyncs on the treo650 (some users only) I use notifications extensively and point them to functions rather than going through launch codes as I assume it's faster (and I'm registering for eventDequeuedNotification') Is this a dengerous programming technique? Could the Operating system be moving my application to a different place and not updating my notification registration? I get the error Emul68KMAin.c, line:403, illegal instruction 792C at address 1116ADBC (final address changes) Should I stick to notifications through launch codes - or is there a way to find out if my db is moved and re-register before an event is diverted to a non-function? Thanks in advance, Rob -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
