Hmm... I can't seem to convince NSNotificationCenter to send the UIApplicationDidFinishLaunchingNotification notification. I suspect somehow externals are loaded after that's sent. I'm not sure. So we are back to apps launching without knowing they are launching in response to a notification.
Anyway, I can (have) created local notifications. It appears the notification badge number is implemented in an odd way. You would assume it would increment but you have to set a specific number. So let's say you setup 10 notifications and assign badge numbers 1-10. If you launch your app after 5 you want to reset the badge number number back to 0 and you want the rest of your notifications to have badge numbers 1-5. So what I'm thinking might be simplest is to maintain a notification list in the app. when you launch your app you clear all the notifications and set the badge number to 0. You show the user any unread notifications in your app and present any new ones from your list if the app is still running when they are due. Then when your app closes you loop over what remains of you list and setup the notifications again. Cheers Monte On 01/02/2012, at 8:03 AM, Thomas McGrath III wrote: > Monte, > > Actually that might still be useful because I can poll for the reason for the > scheduled notif and react accordingly. I just don't know how useful….. _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
