-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
One swipe moves multiple views #10
Comments
I have inspected this and it was because I used ViewHolder pattern, recommended by Google. When "convertedView" was not null in adapter's getView(..) method, the listview was not creating a new view, but using an existing one, and hence the problem |
You mean that when you swipe one view you can observe few other views also move at the same time? This seems to be either issue with adapter or touch event handing on your side. I'm not sure if there is anything that could be causing this on library side. Please try to investigate this further and let me know if you find anything. |
RecyclerView uses view holder pattern so it should be no different. Did I misunderstand something in your issue? |
No, you did not. I replied to the issue on github
Pe 5 sept. 2017 17:25, "Łukasz Rutkowski" <notifications@github.com> a
scris:
… RecyclerView uses view holder pattern so it should be no different. Did I
misunderstand something in your issue?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#10 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AXf2kinYq5-2NPiqy8efKmp2YaTAeiXrks5sfVnugaJpZM4PM_sG>
.
|
I think I understand now. You were keeping views in scrolled state by returning false in gesture listener methods. And when you scrolled your ListView then the newly bound views would keep the state of other views. You probably fixed that by calling I'm closing this issue as that was user error. The views behaved correctly. |
Yes, you can close it. Thank you for your patience and reponsivity. And for
the project, too :D
Pe 5 sept. 2017 18:03, "Łukasz Rutkowski" <notifications@github.com> a
scris:
… I think I understand now. You were keeping views in scrolled state by
returning false in gesture listener methods. And when you scrolled your
ListView then the newly bound views would keep the state of other views.
You probably fixed that by calling moveToOriginalPosition().
I'm closing this issue as that was user error. The views behaved correctly.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#10 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AXf2knT3kX8k2nUAMM_AHBVk_XBzSLtVks5sfWKZgaJpZM4PM_sG>
.
|
Having 10 SwipeActionViews in a ListView using a coustom adapter, swiping a view changes other also: number 0 changes number 7, 1 changes 8.
When having 35 views , swiping a view cause other 4 to swipe, one every 7 views.
I haven't inspected it yet
The text was updated successfully, but these errors were encountered: