I recently came across a side effect of ExgRegisterDatatype() that cost me several hours. (And a few user complaints that we did not understand for quite some time.)
The problem is that ExgRegisterDatatype() undoes the effect of previous call to ExgSetDefaultApplication() if both were applied to the same creatorId. And this is done even in the case if the ExgRegisterDatatype() just re-registers the old information. (We did this thinking that we just increase the safety - however, the opposite was true.) The worst of all is that the testing may not reveal the problem. ExgGetDefaultApplication() may return your creatorId even if your app isn't the default handler. This happens when: 1. there is no default handler (logical consequence of the ExgRegisterDatatype() if your app was the default handler before the call) 2. your app happens to precede competing handlers in the preferences Maybe this helps somebody with similar problems, as we perceived. Or the SDK documentation could be improved to avoid the confusion. Jan Slodicka -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
