Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You need a receiver definition for each type in your manifest file like:</p> <pre><code> &lt;receiver android:name=".MyWidget" android:label="@string/medium_widget_name"&gt; &lt;intent-filter&gt; &lt;action android:name="android.appwidget.action.APPWIDGET_UPDATE" /&gt; &lt;/intent-filter&gt; &lt;meta-data android:name="android.appwidget.provider" android:resource="@xml/medium_widget_provider" /&gt; &lt;/receiver&gt; &lt;receiver android:name=".MyWidget" android:label="@string/large_widget_name"&gt; &lt;intent-filter&gt; &lt;action android:name="android.appwidget.action.APPWIDGET_UPDATE" /&gt; &lt;/intent-filter&gt; &lt;meta-data android:name="android.appwidget.provider" android:resource="@xml/large_widget_provider" /&gt; &lt;/receiver&gt; </code></pre> <p>This would allow you to have the same <code>AppWidgetProvider</code> class be used for multiple widgets, with different widget names and different sizes defined in the <code>&lt;appwidget-provider&gt;</code> XML.</p> <p>Now if you need more differences in your widgets than what is in the <code>&lt;appwidget-provider&gt;</code> XML I would create a base widget class that implements all the common behavoir between the different types:</p> <pre><code>public abstract class MyBaseWidget extends AppWidgetProvider </code></pre> <p>And then each of your concrete implementations could extend MyBaseWidget. Then in your manifest file you would have a receiver definition for each of your concrete implementations like:</p> <pre><code> &lt;receiver android:name=".MyMediumWidget" android:label="@string/medium_widget_name"&gt; &lt;intent-filter&gt; &lt;action android:name="android.appwidget.action.APPWIDGET_UPDATE" /&gt; &lt;/intent-filter&gt; &lt;meta-data android:name="android.appwidget.provider" android:resource="@xml/medium_widget_provider" /&gt; &lt;/receiver&gt; &lt;receiver android:name=".MyLargeWidget" android:label="@string/large_widget_name"&gt; &lt;intent-filter&gt; &lt;action android:name="android.appwidget.action.APPWIDGET_UPDATE" /&gt; &lt;/intent-filter&gt; &lt;meta-data android:name="android.appwidget.provider" android:resource="@xml/large_widget_provider" /&gt; &lt;/receiver&gt; </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POhow to add multiple widgets in one app?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USMark B
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POhow to add multiple widgets in one app?
      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
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COHi, thanks for your answer. But it seems that I cannot share the same widget provider. (if I do, only first in manifest is shown). So, basically, multiple widget providers would be the answer for me. Is anyone working with one widget provider?
      singulars
      1. PO
      1. USxandy
    2. COYep, just followed above instructions and found it only works if i specify different widget provider classes. Good anyway, thanks everyone! :)
      singulars
      1. PO
      1. USdimsuz
    3. COSame here, need multiple widget provider classes for widgets to show up.
      singulars
      1. PO
      1. USchakrit
 

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