So I'm using a modified version of the SectionedAdapter and it seems to be working quite well. The only issue is that I want to let each "section" adapter to determine the clickability of it's items. It seems like with the SectionedAdapter, all items except the headers are clickable. How exactly would I modify SectionedAdapter.isEnabled() to use the corresponding section's isEnabled()? I've spent time looking at the methods used for getItem(), getViewType(), and getView() which seem to do similar things, but honestly don't quite understand what's being done... Thanks again for all your help!
On Jul 7, 11:51 am, "Mark Murphy" <mmur...@commonsware.com> wrote: > > So are you saying I need to revert back to my original method of using > > a ListView with a custom adapter and add my "pre-list" content Views > > to the adapter itself? > > No, and I'm not sure, respectively. > > First, in terms of "need", I'm not saying you need to do anything. You > said you wanted a UI like the one screen in Android Market, and I > indicated how I would build it. It may be there is a way to achieve your > desired result from your current base. > > Second, I don't know what you mean by "'pre-list' content views" with > respect to my description. If you mean fixed items, like the logo pane or > the Open/Install pane in the Android Market screen, those are not in the > adapter because they are not in the scrolling list. If, on the other hand, > you're referring to various bits of things in the scrolling area (e.g., My > Rating versus user comments versus other entries in the Android Market > screen list), then yes, they would be returned as rows by the adapter. > > For example, Jeff Sharkey wrote up a post shortly before he was enGoogled, > demonstrating creating a ListView that looks like a UI for > SharedPreferences: > > http://jsharkey.org/blog/2008/08/18/separating-lists-with-headers-in-... > > His code probably still works, though it was for Android 0.9 and so your > kilometerage may vary. I have my own spin on his example, up to date for > Android 1.5, which you can download as part of the source code from: > > http://commonsware.com/AdvAndroid/ > > Both his and mine are focused on things that are mostly data, culled from > multiple adapters, with headings. I'd approach the Android Market scenario > a bit differently, but using the same underlying tools (e.g., > getViewTypeCount(), isEnabled()). > > Note to self: the Android Market scenario would be a nice example for a > future book revision... ;-) > > -- > Mark Murphy (a Commons Guy)http://commonsware.com > Android App Developer Books:http://commonsware.com/books.html --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
