StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
19563750
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2013-10-24T10:45:24.827
FavoriteCount
0
LastActivityDate
2016-01-22T10:06:53.570
LastEditDate
2016-01-22T10:06:53.570
LastEditorUserId
637545
OwnerUserId
637545
ParentId
19556702
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
Update: My original solution below will work for this use case, but a much better solution is that of the <code>ViewHolder</code> pattern, as touched on by HailNaRoz. Although it isn't explained by HailNaRoz why his solution works, that solution uses a <code>ViewHolder</code> to aid <code>View</code> reuse and is the preferred method adopted by Google and the Android Dev community. The <code>ViewHolder</code> keeps a reference to the <code>Views</code> (<code>EditText</code>, <code>TextView</code>, <code>ImageView</code> etc), and allows you to add them back into the correct list row when it becomes visible. Its also worth looking at <code>RecyclerView</code>, which has since been introduced to aleviate some of these issues, which forces this methodology. <code>RecyclerView</code> is available as a support library that can be added in gradle See <a href="http://developer.android.com/training/improving-layouts/smooth-scrolling.html#ViewHolder" rel="nofollow">View Holder in List View</a> and <a href="http://developer.android.com/training/material/lists-cards.html" rel="nofollow">Creating Lists and Cards (Recycler View)</a> Original: Your problem is that your <code>EditText</code> is being recycled. You are keeping hold of a copy of your <code>TextView</code> text and resetting it every time it is loaded, but not for your <code>EditText</code>. So you need a way to store the text in the <code>EditText</code> field and reset it in your <code>getView()</code> method. To do this you want to set up a <code>TextWatcher</code> after your if/else statement in <code>getView()</code>: <pre><code>holder.editText.addTextChangedListener(new TextWatcher() { public void onTextChanged(CharSequence s, int start, int before, int count) { } public void beforeTextChanged(CharSequence s, int start, int count, int after) { } public void afterTextChanged(Editable s) { editTextList.put(position,s.toString()); } }); </code></pre> This stores the value in a <code>HashMap</code> maintained separately. <code>position</code> is taken from the int parameter in your <code>getView()</code> method. You will need to make it final. The <code>HashMap</code>: <pre><code>private HashMap<Integer,String> editTextList =new HashMap<Integer,String>(); </code></pre> Then when you set your <code>TextView</code> text you also want to set the <code>EditText</code> value: <pre><code>holder.text.setText(s); holder.editText.setText(editTextList.get(position)); </code></pre> This should keep the current positions <code>editText</code> value in the correct <code>EditText</code> box.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POAndroid List View duplicates Edit Text values on scrolling
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USbiddulph.r
UserOwnerUserId
1. USbiddulph.r
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. COThanks Biddulph for the reply. But its not working for me. Is it working for you ?
 singulars
 PostPostId
 PO
 UserUserId
 USakashPatra
2. COThis setup is working for me. Have you tried debugging and making sure that values going in/out of the editTextList are present, and that the TextWatcher listener is being hit properly?
 singulars
 PostPostId
 PO
 UserUserId
 USbiddulph.r

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.