I get it now. Thanks for the explanation.
I also just realized that the implementation of setOrderedHint() in
BroadcastReceiver is a no-op in ICS code-base. All it contains is a comment
stating that this method was accidentally left over in the SDK.
checkSynchronousHint() now checks for the
Bump!
I'm still looking for clarification on this comment:
using BroadcastReceiver as a separated class not known by the rest of the
framework
On Friday, 18 May 2012 12:27:38 UTC+5:30, Kiran Rao wrote:
Dianne,
I'm not sure I fully understand this phrase in your comment:
using
On Thu, May 17, 2012 at 11:57 PM, Kiran Rao techie.curi...@gmail.comwrote:
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
Dianne,
I'm not sure I fully understand this phrase in your comment:
using BroadcastReceiver as a separated class not known by the rest of the
framework
To clarify, my current solution is a fork of the support package's
LocalBroadcastManager. It does *not* use setOrderedHint(). Because of
I am trying to add ordered broadcasting functionality to
LocalBroadcastReceiver class. I just noticed this method:
http://developer.android.com/reference/android/content/BroadcastReceiver.html#setOrderedHint(boolean)
The docs have this to say :
For internal use, sets the hint about whether
No, you should not be using it. Why would you even *want* to use it? I
can only imagine using this to do things that are broken. :)
On Thu, May 17, 2012 at 6:06 AM, Kiran Rao techie.curi...@gmail.com wrote:
I am trying to add ordered broadcasting functionality to
LocalBroadcastReceiver
On Thu, May 17, 2012 at 4:27 PM, Dianne Hackborn hack...@android.com wrote:
No, you should not be using it. Why would you even *want* to use it? I can
only imagine using this to do things that are broken. :)
To clarify (and fix a typo in Kiran's post), he is working on adding
ordered
Oops .. apologies for the typo, and the ensuing confusion. I did mean
LocalBroadcastManager in my original post, wherever I referred to
LocalBroadcastReceiver.
Mark has summed it all up in his response. My current implementation is
this:
try to fork BroadcastReceiver and use a forked edition
Hm, okay, for that, where basically you are just using BroadcastReceiver as
a separated class not known by the rest of the framework, it seems okay.
On Thu, May 17, 2012 at 7:22 PM, Kiran Rao techie.curi...@gmail.com wrote:
Oops .. apologies for the typo, and the ensuing confusion. I did mean
9 matches
Mail list logo
