Databases
StackOverflow2013
Postsdbo
POWhen to use BroadcastReceiver for non-cross-application communication?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POWhen to use BroadcastReceiver for non-cross-application communication?
    primarykey
    data
    text
    <p>Are there any use cases in which I would want to use a BroadcastReceiver for something other than cross-application communication?</p> <p>After reading the <a href="http://developer.android.com/reference/android/support/v4/content/LocalBroadcastManager.html" rel="nofollow noreferrer">documentation</a>, it seems like they are targeted at cross-application communication, but the idea of using them with the LocalBroadcastManager is also mentioned. I also read <a href="https://stackoverflow.com/questions/5296987/what-is-broadcastreceiver-and-when-we-use-it">this post</a>, which addresses the general usage of broadcast receivers. Neither seem to hit clearly on why it would be useful to use broadcasts and receivers for anything other than cross-application communication. </p> <p>Does it have anything to do with their asynchronous nature, or maybe they're just used to move some processing out of the main activity?</p> <p><strong>Clarification:</strong> I guess the term cross-application was too general. I was considering the built-in actions such as </p> <pre><code>android.hardware.action.NEW_PICTURE </code></pre> <p>to be coming from applications. What I would like to know is: when is it useful to use a BroadcastReceiver for communication within my app - I guess this would narrow it down to custom intent actions/categories. Sorry if the way I'm asking this is confusing. I've only just recently begun programming with Android and I still don't understand the OS very well.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCommunity
    1. USMack
    plurals
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload