Databases
StackOverflow2013
Postsdbo
POAndroid: ListView elements with multiple clickable buttons
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POAndroid: ListView elements with multiple clickable buttons
    primarykey
    data
    text
    <p>I've a <code>ListView</code> where every element in the list contains a TextView and two different Buttons. Something like this:</p> <pre><code>ListView -------------------- [Text] [Button 1][Button 2] -------------------- [Text] [Button 1][Button 2] -------------------- ... (and so on) ... </code></pre> <p>With this code I can create an <code>OnItemClickListener</code> for the whole item:</p> <pre><code>listView.setOnItemClickListener(new OnItemClickListener() { @Override public void onItemClick(AdapterView&lt;?&gt; list, View view, int position, long id) { Log.i(TAG, "onListItemClick: " + position); } } }); </code></pre> <p>However, I don't want the whole item to be clickable, but only the two buttons of each list element.</p> <p>So my question is, how do I implement a onClickListener for these two buttons with the following parameters:</p> <ul> <li><code>int button</code> (which button of the element has been clicked)</li> <li><code>int position</code> (which is the element in the list on which the button click happened)</li> </ul> <hr> <p><strong>Update:</strong> I found a solution as described in my answer below. Now I can click/tap the button via the touch screen. However, I can't manually select it with the trackball. It always selects the whole list item and from there goes directly to the next list item ignoring the buttons, even though I set <code>.setFocusable(true)</code> and <code>setClickable(true)</code> for the buttons in <code>getView()</code>.</p> <p>I also added this code to my custom list adapter:</p> <pre><code>@Override public boolean areAllItemsEnabled() { return false; } @Override public boolean isEnabled(int position) { return false; } </code></pre> <p>This causes that no list item is selectable at all any more. But it didn't help in making the nested buttons selectable.</p> <p>Anyone an idea?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USznq
    1. USznq
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    3. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POAndroid: ListView elements with multiple clickable buttons
      1. USMojo Risin
      1. VTFavorite
    2. VO
      singulars
      1. POAndroid: ListView elements with multiple clickable buttons
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POAndroid: ListView elements with multiple clickable buttons
      1. USEmanuil Rusev
      1. VTFavorite
    1. COAre these still needed ?
      singulars
      1. POAndroid: ListView elements with multiple clickable buttons
      1. USStuart Axon
    2. COIf you look at the BaseAdapter code, you'd see that areAllItemsEnabled() and isEnabled() are just hardcoded to true, making them simple placeholders without any logic.
      singulars
      1. POAndroid: ListView elements with multiple clickable buttons
      1. USArtem Russakovskii
    3. COWhat if I want to use a SimpleCursorAdapter?Do I have to make a custom adapter extends simplecursoradapter ?
      singulars
      1. POAndroid: ListView elements with multiple clickable buttons
      1. USoratis
 

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