On Aug 13, 2012, at 9:12 PM, bob <b...@coolfone.comze.com> wrote: > So, I guess you don't have to use a text view? Then why do all the > constructors take a textViewResourceId? What should I pass in for that if > I'm not really going to use a text view?
If you're lucky it's only getView(…) that uses textViewResourceId and it shouldn't matter what value you give constructor. But to be safe it might be best to use actual TextView resource id. Quite obviously rationale for asking a textViewResourceId in every constructor comes from the fact default implementation uses it somewhere. Possibly elsewhere than getView(…) only too. -- H -- 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
