I would agree that posting a vchr event into the key queue is not by itself an appropriate notification mechanism. The key queue is good in that it survives app switches and is thread safe. However, the event can be lost in an event loop that is not in your control. While you can work hard to avoid most of these, there will always be one or two dialogs that are still causing problems, such as the low battery dialog and the attention manager dialog. An API you can call to poll the MSR library would be appropriate.
Other alternatives: callback or sub-launch. With a callback, you'd pass the address of a routine in your app to a setup API, and it would call the routine when data was ready. This requires the routine to stay locked and loaded, which is a bit of a pain. With a sub-launch, the setup API would be given the info needed to identify your application, and it would sub-launch the app with a specific launch code to inform you that data was ready. Of course, none of this makes your job any easier -- unless you can convince the authors of the MSR library to update it. -- Peter Epstein -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
