OK, well I give up then. I have done some testing in various scenarios and have found that this is simply inconsistent. My view hierarchy is not incredibly complex, nor is it particularly deep. What I do see is that some times my checkmarks display properly, then after displaying properly once in the application, they then display correctly elsewhere, but sometimes they even display where they shouldn't, specifically where I replaced some CheckedTextViews with my own implementation of Checkable based on RelativeLayout since I had to display other elements too. Sometimes, even though the checkmark displays properly on normal view, when pressing the item in a list, the checkmark expands to fill the list item. Even in an extremely simple layout I found that includes a CheckedTextView or derived class does not play nice in LinearLayout, particularly when a ListView is also in the Layout. In RelativeLayout, the CheckedTextView only plays nice when included before the other elements. So, it turns out I will be completely dumping the CheckedTextView in favor of my own custom drawn checkable and rewriting my application to avoid the inconsistency of the CheckedTextView. Note all of this worked perfectly fine until 1.5 so, apparently, something has gone haywire in this iteration.
On Apr 29, 10:47 pm, "nEx.Software" <justin.shapc...@gmail.com> wrote: > Anybody? Now that T-Mobile appears to be releasing 1.5 OTA, this will > begin to become an issue quickly I think. > My users won't be able to see what they have selected. > > On Apr 29, 12:47 pm, "nEx.Software" <justin.shapc...@gmail.com> wrote: > > > No worries. Any idea why my checkmarks disappear in 1.5? > > In my XML I have the following attribute: > > android:checkMark="@drawable/btn_check" > > > btn_check is a stateful drawable but it seems maybe the states have > > changed or something because if I just set the checkmark to a static > > drawable it displays the checkmark fine. Obviously, I want to be able > > to continue using the stateful drawable. Any ideas? > > > On Apr 29, 11:45 am, Romain Guy <romain...@google.com> wrote: > > > > Doh! Apparently LayoutInflater lets you inflate abstract classes. I'll > > > fixed CheckedTextView to not be abstract anymore. Sorry for that. > > > > On Wed, Apr 29, 2009 at 11:41 AM, Romain Guy <romain...@google.com> wrote: > > > > CheckedTextView has always been abstract. You cannot and could not > > > > instantiate it from code but you can use it from XML yes. This has not > > > > changed from 1.1 to 1.5. > > > > > On Wed, Apr 29, 2009 at 11:10 AM, nEx.Software > > > > <justin.shapc...@gmail.com> wrote: > > > > >> I was able to include it in my XML Layout file in 1.1. So to continue > > > >> using it, I'll have to extend it? And reimplement the functions that > > > >> were already provided to me in the last SDK? It is incredibly > > > >> frustrating when, per instructions from the Android engineers, I > > > >> followed what was in the SDK and now it no longer works. Thanks for > > > >> the info, guess I'll Just extend it and go from there. > > > > >> On Apr 29, 10:57 am, Romain Guy <romain...@google.com> wrote: > > > >>> CheckedTextView is an abstract class, just as it was in Android 1.1. > > > >>> This means you cannot instantiate it directly. > > > > >>> On Wed, Apr 29, 2009 at 10:52 AM, nEx.Software > > > > >>> <justin.shapc...@gmail.com> wrote: > > > > >>> > So I tried to test CheckedTextView in a new project based on 1.5 and > > > >>> > it doesn't even show as an option. tried to create in code via > > > >>> > CheckedTextView CTV = new CheckedTextView(this); but it cannot be > > > >>> > instantiated, so how do we use CheckedTextView in the new SDK? What > > > >>> > gives? > > > > >>> > On Apr 28, 7:15 pm, "nEx.Software" <justin.shapc...@gmail.com> > > > >>> > wrote: > > > >>> >> Seems 1.5 has changed CheckedTextView where the android:checkmark > > > >>> >> xml > > > >>> >> no longer works? Also, the documentation appears to say indicate > > > >>> >> the > > > >>> >> checkmarkdrawable only is drawn when checked but does this mean > > > >>> >> there > > > >>> >> is no uncheckeddrawable?I'm not able to check in my project at the > > > >>> >> moment but it certainly seems this is the case. My UI broke, I know > > > >>> >> that much. Any thoughts? > > > > >>> -- > > > >>> Romain Guy > > > >>> Android framework engineer > > > >>> romain...@android.com > > > > >>> Note: please don't send private questions to me, as I don't have time > > > >>> to provide private support. All such questions should be posted on > > > >>> public forums, where I and others can see and answer them > > > > > -- > > > > Romain Guy > > > > Android framework engineer > > > > romain...@android.com > > > > > Note: please don't send private questions to me, as I don't have time > > > > to provide private support. All such questions should be posted on > > > > public forums, where I and others can see and answer them > > > > -- > > > Romain Guy > > > Android framework engineer > > > romain...@android.com > > > > Note: please don't send private questions to me, as I don't have time > > > to provide private support. All such questions should be posted on > > > public forums, where I and others can see and answer them --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
