On Sat, Mar 10, 2012 at 9:55 AM, RedBullet <[email protected]> wrote: > Awesome. Where can I buy your book? Seriously?
http://commonsware.com/warescription ------------------- Getting back to your current problem, the notion that certain rows are "special" and need different rendering is really part of your data model, even if it is perhaps not a *persistent* portion of the data model. After all, if you modify a row View manually, outside the adapter, what happens when the user scrolls? First, your manual changes, unless overridden by your adapter, will affect random other rows via recycling. Second, if the user scrolls your special rows back into the screen, the odds are decent that they will be rendered using different Views (again, due to recycling) and your special formatting won't be there. The only safe way to adjust the rows, therefore, is if the adapter does it as part of its natural business logic and takes it into account as rows are recycled. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy _Android Programming Tutorials_ Version 4.1 Available! -- 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
