You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fantastic tools! One thing I was hoping to learn was whether it is possible to specify a different background drawable for each item in the list's adapter. In my example I want to color code comments. So I either want: mQuickActionSetup.setBackgroundResource(R.drawable.comment_background_blue);
or mQuickActionSetup.setBackgroundResource(R.drawable.comment_background_red);
However if I specify this in the getView method, all the comments will have the background of the last value specified. Could you point me in the right direction for modifying your library to support multiple backgrounds for the hidden view?
On the same topic, specifying differing drawables for the action item icons that are revealed in each list item would also be a welcome addition.
Thanks!
Brian
I'm working on that. Hope to commit API extension soon...
The text was updated successfully, but these errors were encountered:
I thought this should be extended in the existing API but there's an simple option:
Just use list view type for that...that's what its actually there for.
I added an (really ugly) example in the showcase which demonstrates how to do that.
Thanks for the update, this turned out to work great.
I would just reiterate to others looking to do this, make sure you override the getViewTypeCount and getItemViewType methods in your adapter. Otherwise all views in the list will be recycled and you will have inconsistant hidden view backgrounds since you can only call setHiddenViewSetup once per view.
No problem, glad I could help.
But I see the problem of the static behavior of the given setup.
I have an extension in mind and will keep improving the API.
Thank for your inspiration and feedback!
Quote of the request:
I'm working on that. Hope to commit API extension soon...
The text was updated successfully, but these errors were encountered: