04-03-2009 12:03 AM
I've been experimenting with the notifications demo and custom consequences to customize LED notifications. The behavior I've seen on my BB Curve 8230 with OS 4.5 so far puzzles me. I've done the standard setup:
The custom Consequence sets the LED to blink purple in startNotification:
I use the standard calls to start/stop the notifications:
When I trigger the event on my phone, the results can be inconsistent. I might see the LED blink purple briefly, then switch to red. Or it might stay purple. Calling cancelImmediateEvent turns off the purple or red light but may or may not restore the green coverage indicator. It seems to me that any custom Consequence clashes with the default consequence that is configured in Profiles, with the result that it is is either cancelled out or it shuts off the coverage indicator light.
04-16-2009 10:19 AM
Modifying the blink pattern using the LED class basically overrides any current LED settings. Since you are integrating with the profiles the appropriate way to handle this is to let the user enable/disable the LED blinking within their profile setting. The "Repeat Notifications" option in the profile setting toggles the blinking of the LED for a notification.
There is no API to return the LED to its previous blinking state after it was changed using the LED class.