Hans wrote: > I have seen that before, but that would require you to run a service > in the background (or always have an activity running) to constantly > to monitor those changes instead of what you're supposed to use, which > is a broadcast receiver...
"Supposed to use" assumes a certain use case. After all, we don't use broadcast receivers to find out about ImageButton clicks. There certainly may be scenarios in which a broadcast receiver would be the preferred implementation, though, and so having this Intent be a part of the API would be a good thing, all else being equal. > Surely this is an accidental oversight by the framework team, no? Certainly not "surely". I'd go with "possibly". For example, if the Intent semantics (e.g., extras passed along with it) are still in flux, they may not want to make it an official part of the API. Or, they may simply have not gotten around to it. There's an impression on these lists that there are an infinite number of core Android team members. The team is rather finite. Or, perhaps, it was an oversight. Since I haven't yet downloaded the 1.5 preview SDK, you might check in there and see if it is public and documented. If it is not, log making that Intent be part of the public API as an issue on http://b.android.com, if it is not already there. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://twitter.com/commonsguy Android App Developer Training: http://commonsware.com/training.html --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
