02-08-2011 03:38 PM
how did i not know about the "undocumented-and-yet-to-be-released Notifications API"!
does indeed sound like a better alternative.
Sometimes us "oldsters" forget that not everyone has been obsessively watching every detail to emerge in the last three months. (Only three for me, so I'm barely even one of the oldsters!)
There has been no official mention of the Notifications API, though I believe it merited a brief comment in some webcast or video but it's not worth tracking that down. Mostly what we know was what was in the first simulator, with a little "flag" icon in the upper left. There was also a number showing, or you could tap on it to see a number, and presumably the details.
See this video, for example, at time 0:15, where you can see it onscreen. And yes, that's basically all we know about it, for now. As John said a long time back, we don't even know for sure it will be there in the final thing. Then again, we know so little, so we have to go with our guesses, which are likely good in this area.
I believe you could skim some info on the Android notifications feature to get a general idea of the type of thing they likely have in mind.
02-08-2011 04:22 PM
wow. you guys are good. really.
i've only seen timer apps on the iphone and none have anything but modal dialogs that i've ever seen. we can do better! (maybe...)
05-20-2011 06:05 PM
Well, all this worked great until the real Playbook came out. My modal dialog box is set as a voluntary user preference to notify the user of an alarm event when the app is in the background. It is only supposed to show when the app gets the deactivate event. If the playbook is set to Application behavior: showcase, then the app is always activated apparently unless the Playbook goes into standby. So the app never gets the deactivate event. At least that is what I think is occuring.
I have this in my blackberry-tablet.xml:
Any workarounds you can think of?
05-20-2011 08:03 PM
05-20-2011 08:22 PM
thanks. i had thought of switching over to that long ago just to make development easier. but i don't think this solves my problem does it? this won't work when the app is deactivated, which is the only time i need the dialog box. i'm a nube so i may be mistaken here...
05-21-2011 09:02 AM