StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
8662545
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-12-28T23:43:24.903
FavoriteCount
0
LastActivityDate
2011-12-28T23:43:24.903
LastEditDate
LastEditorUserId
0
OwnerUserId
246461
ParentId
8662271
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
It depends somewhat on what you are looking to accomplish... If you are looking to display a third background type when the user has two fingers down, there is no drawable state that you can reference directly to accomplish. You would have to co-op one of the existing states that is not often used in touch mode (such as the selected state), and implement a custom touch handler on the list item's object to set that state. For example, implement <code>onTouchEvent()</code> in each list item's view (or add an <code>onTouchListener()</code> if you don't have a custom class), look for the <code>ACTION_POINTER_DOWN</code> event to tell you that a second finger came down, and call <code>setSelected()</code> on the view to trigger a drawable you have set for the <code>android:state_selected</code> in your <code><selector></code>. If you just want the state to clear under this case, you can cancel the touch event when more than one finger is detected. In this case, you are looking at customizing the <code>ListView.onInterceptTouchEvent()</code> method to look for the <code>ACTION_PONTER_DOWN</code> event and return <code>true</code>. This will teach the <code>ListView</code> to steal the touch back from it's child item with a second finger, which will cancel the pressed state of the list item. Make sure to call back through to <code>super</code> in this case so you don't break all the existing logic <code>ListView</code> uses for scrolling, etc. Beware of cases where the existing <code>AbsListView</code> implementation may get in your way here. For example, the current implementation of <code>onIntercepTouchEvent()</code> looks for <code>ACTION_POINTER_UP</code> in order to switch the main touch finger from the first to the second. This behavior may cause strange artifacts in your customization if you aren't aware of it. HTH.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POAndroid StateListDrawable Remains Pressed After MultiTouch
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USDevunwired
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POAndroid StateListDrawable Remains Pressed After MultiTouch
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
CommentsPostId
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.