>Actually, newView() should just create the empty views, so bindView() can >be used for binding in either the new-view or recycled-view cases.
yes, either newView() shouldn't be passed a Cursor, implying that bindView() will set it up later, or newView() and bindView() should be exclusive inside getView(). >Given the regression this would require, it is simpler if we just set up >our newView() and bindView() implementations to deal with this particular >aspect of CursorAdapter. well, if everyone is doing it the "wrong" way by copying Cursor to View in both, then we can change it and everyone's list views will suddenly get a bit faster :-) i agree t'is risky though. >Note that I had this screwed up in an earlier edition of one of my books, >so some of the confusion may be my fault. :-( although i do have your books, i have not had 2 minutes to crack them, so you get off scot-free on this one. -- jason.vp.engineering.particle --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
