Hmm... I may just have to trademark those names... thanks ;) "Bob"
Brandon Roberson wrote:
As the system guarantees that only one database of the 'appl' type can have a particular creator ID, you should use that as your key. LocalID could concievably change after a system restore, as you pointed out, and nothing else is guaranteed to be unique. Also, some products go through name-changes as they mature, but the developers don't usually choose a new creator ID as they want the new version to replace the old. Your app shouldn't care if "Bob's Scientific Calculator" becomes "Bob's SuperCalc" when the user upgrades to get the new graphing features. Just tracking the creator ID will allow it to keep working with your app, saving the user the effort of "fixing it" in your app manually.
Best of luck! Brandon
On Mon, 14 Feb 2005 18:06:39 -0000, Luc Le Blanc <[EMAIL PROTECTED]> wrote:
I want to let the user select the (scientific) calculator he prefers to call from within my program. I thus want to offer a popup trigger exactly like those in the built-in Prefs program where you select the program to assing to hardware buttons.
Using SysCreateDataBaseList, I can create a list of all 'appl' DBs on the device. How should I store the user selection? The creator ID or the name? I understand that if I store the name, I can later call DmFindDatabase to find the LocalID and launch it, but what if there were more than one Db with that name? Would storing the LocalID better? Or would it change if there were a hard reset on the device? How does PalmOS store the apps button assignments in its prefs program?
-- Luc Le Blanc -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
-- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
