On Thu, May 17, 2012 at 11:57 PM, Kiran Rao <[email protected]>wrote:
> using BroadcastReceiver as a separated class not known by the rest of the >> framework > > My intention is to alleviate this problem by using setOrderedHint() in my > fork of LocalBroadcastManager. If I do this, I will be able to use the > regular android.content.BroadcastReceiver. and do away with the custom > BroadcastReceiver class. The intention, thus, is to *not* use > BroadcastRecaiver as a separate class; but rather use the one known to the > framework. > LocalBroadcastManager is not part of the framework. It is a separate helper class in the support library. As long as you are not using these classes with the on-device framework (registering in your manifest, Context.registerReceiver(), etc) then I think you will be fine. -- Dianne Hackborn Android framework engineer [email protected] Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
