The expandable lists are working out great, thanks! :^)
If anyone down the line happens to know what's wrong with the original
code above, though, I'd still appreciate understanding what it was
doing incorrectly.
--
You received this message because you are subscribed to the Google
Groups
On Tue, Feb 16, 2010 at 10:47 PM, whicken whic...@gmail.com wrote:
Here's my GroupedListAdapter class, if that helps any - I added the
getStableIds returning false in case there was any extra caching going
on:
Here's a question - what's the purpose of this adapter? What kind of layout
/
I'm just trying to do a grouped layout - so a header would be followed
by a bunch of rows, then another header, and another bunch of rows.
They aren't collapsable, so I don't think it's quite an
ExpandableList. As far as break points go, the only thing that seems
to be called before the crash is
On Wed, Feb 17, 2010 at 8:34 AM, whicken whic...@gmail.com wrote:
I'm just trying to do a grouped layout - so a header would be followed
by a bunch of rows, then another header, and another bunch of rows.
They aren't collapsable, so I don't think it's quite an
ExpandableList.
I would still
If I can believe the debugger, my getView function is never called
between notifyDataSetChanged and the crash. The only calls to my
adapter are three calls to getCount, which in my main test case happen
to return 13. (There's a group of 7, and group of 4, and two
headers). I had 24 entries
Here's my GroupedListAdapter class, if that helps any - I added the
getStableIds returning false in case there was any extra caching going
on:
public class GroupedListAdapter extends BaseAdapter {
ArrayAdapterString headers;
ListAdapter sections;
public GroupedListAdapter(Context
6 matches
Mail list logo
