> > Note that dragging an application onto POSEr won't trigger
> this launch code.
> Any idea how I can debug processing this launch code when the app
> is
> being first installed? I'm using CodeWarrior
Scott, a few items which may be of help:
1. I have an app which performs sorting on > 40 databases after a HotSync.
To keep from having to HotSync over and over while testing, I wrote a little
app which had one big button: "Send HotSync Notify To <myapp>" and when it
is pressed, it sub-launches my app w/ the HotSync notify code. Very handy.
You should be able to throw together a little test app that does the same
for your app in a few minutes.
2. Now that you can send HS notification messages to your app at will, debug
your app on POSE using CW. Once you are up and running, exit the app on
POSE and put a breakpoint in CW on the HS notify handler in your code.
Launch your little tester app from step 1, and hit the button . . . CW
should stop the program at your HS notification handler where you can trace
through and see what's going on. This worked great for me in figuring out
several bugs (remember, no global vars or function calls out of CODE segment
1 . . . doh!).
I don't know if this would work for the soft-reset . . . I haven't tried
that yet. Please let the list know if it does.
Cheers,
-DGA
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
