ragunathjawahar / adapter-kit Goto Github PK

Currently InstantCursorAdapter only supports POJOs. Create a mechanism that leverages the capabilities of Cursor.

When inflating the section header layout, the parent ViewGroup should be supplied:
View.inflate(mContext, mSectionHeaderLayoutId, parent);

Currently, null is passed as the parent, and the section header's layout params are ignored. The easiest work around I've found is to add a wrapper LinearLayout or RelativeLayout to the section header layout.

It seems to me that the SimpleSectionAdapter should be listening for changes on the wrapped adapter. That is, if the underlying adapter's data changes, then SimpleSectionAdapter should know to update its sections.

Something like having the SimpleSectionAdapter call registerDataSetObserver() on the wrapped adapter, and then calling findSections in the onChanged() callback.

can you public InstantAdapterCore class? so I can use it's bind method.

Your table looks great and it didn't take long to set up the example using Android Studio. This line caused an error that I did not understand at first. After I commented it out, things were fine.

    //? import com.mobsandgeeks.adapters.R;

It was probably not needed because of how Android studio builds using the Gradle compile line. So the only files I needed to make a test project were ArrayAdapterDemoActivity.java, list_view.xml and section_header.xml.

Thanks.

Hello, in my project, I have to override SimpleSectionAdapter to change style of the section background. Is there a way to do this properly ?

In my case, I override the getView method, do the switch again, and set the background color on my view. To do this I have to create another mContext field and constant VIEW_TYPE_SECTION_HEADER because there are private.

Thx

Android id resources are not final in library projects (see http://tools.android.com/tips/non-constant-fields)

It would be helpful if there was a way to link methods -> views other than using the view id.

This works great for going down in the list but backwards it's just like a normal list and hits the start. Is there a way to make it work similar the other way around as when scrolling down? Or I have to scroll down far enough when opening the fragment so I'm sure the user wont scroll whole way back to the start? Thanks