On Sun, May 1, 2011 at 12:48 AM, Romain Guy <romain...@android.com> wrote: > You could, but setTag(int, Object) forces you to use unique ids throughout > your app.
Well, now, that's a remarkably gentle response. I seem to recall you being a bit more... forceful, shall we say, when I suggested using the two-parameter setTag() to avoid having to fuss with a holder class. Something about it wasn't there for app developers but rather for libraries, or some such. As a result, I destroyed that section of the book and salted the earth it sprang from. :-) Are the indexed getTag()/setTag() save for app developer consumption? And, if so, what rules should we be following? Thanks! -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy _Android Programming Tutorials_ Version 3.4 Available! -- 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