DGA described one way to debug your sync notify handling code that should
work just fine. You should be able to set up the emulator to be able to
HotSync, and do the real thing as well. For debugging code that runs on a
soft reset, I found actually resetting the emulated device to be an
unreliable method. Sometimes it would stop in breakpoints set in the reset
notification handling code, but after a lot of crashes, I changed my
strategy. You don't want to do much on a reset notification anyway, since if
this code fails, most users won't have any recourse other than a hard reset,
which leads to some data loss. The up arrow reset isn't something we tell
users about. To debug the little bit of code you do keep in the reset
notification, I recommend either writing a simple app that sends the
notification to your app, or adding some way to invoke the code from within
the app, on debug builds. The former seems cleaner to me. In fact, a general
purpose app that sends a user selected launch code to a user selected
application could make a nice litte utility. Enter the creator code of the
app in a field, and hit a button to send a reset notification, another
button to send a sync notify, etc.
--
Peter Epstein
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
