Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <blockquote> <p>At this point I am just thinking about making an inner class <code>BroadcastReceiver</code> in each activity and putting the desired functionality in those</p> </blockquote> <p>Yep, this is the best way to implement that feature. If you want to make the functionality common rather than copying it into each Activity, you could create a base class for each Activity in the application to extend if you want the <code>BroadcastReceiver</code> to be an inner class.</p> <p>You can also still define it in a separate file as you likely already have, but just register the receiver directly in each Activity rather than once in the AndroidManifest.xml file. If you register/unregister the receiver in <code>onResume()</code>/<code>onPause()</code>, then you will still only have one active receiver at any given time which is attached to the currently foreground Activity. <strong>These methods also keep you from receiving the given broadcast when your app isn't in the foreground at all, whereas a receiver defined in the manifest is always active, forcing you to handle that case.</strong></p> <p>If you need to explicitly pass some identifier to each instance of the <code>BroadcastReceiver</code> as to which Activity it's associated with, define a simple identifier (like the class name as a String) that you can check in the receiver. It's not a good idea to pass the Activity itself, for similar reasons as to why the framework doesn't do that either. If you're curious, I wrote a <a href="http://www.doubleencore.com/2013/06/context/" rel="nofollow">blog post</a> not long ago detailing some of the issues with passing around Context like that.</p>
    singulars
    1. This table or related slice is empty.
    1. POBroadcastReceiver performing different actions based on Activity running
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USDevunwired
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POBroadcastReceiver performing different actions based on Activity running
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COOkay, I thought this was the cleanest way to do this. I'm also interested in receiving broadcasts while the application is not in the foreground. What I'm thinking of doing is registering a global `BroadcastReceiver` in the manifest, which will send out an appropriate and application specific ordered broadcast, which can get picked up and handled by the running activity. If you have any comments on this let me know, otherwise I will try it out and see which works best.
      singulars
      1. PO
      1. USajar1189
    2. COHave a look at `LocalBroadcastManager` for the secondary part, it will be more efficient than a global broadcast: https://developer.android.com/reference/android/support/v4/content/LocalBroadcastManager.html
      singulars
      1. PO
      1. USDevunwired
    3. COIf you only deliver it to the running Activity, making the broadcast ordered is also unnecessary overhead.
      singulars
      1. PO
      1. USDevunwired
 

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