Hi Romain , Sorry for the repeated message as I guess my first message went to just one person.
I have following two questions related to AbsSpinner and I expect you can clarify the situation here. 1. In my application I have extended AbsSpinner class and after compiling in eclipse and sdk . The application works fine on emulator or on phone. But when I compile the same application against Platform Source Code I get an error message for layout(int delta, boolean animate) method which is an abstract method and not a protected one for which I can override it. How to resolve this issue? Why in first case I did not get such error message? 2. In your reply (above) you mentioned just copy/paste the code in your application. I'd like to know which code you are referring to? Is the AbsSpinner class code? Thanks in advance argongold On Tue, Jul 20, 2010 at 2:01 PM, Romain Guy <[email protected]> wrote: > AbsListView and AbsSpinner are designed to be extended within the > framework. They could also be extended in 3rd party apps but we did > not expose all the necessary protected fields and methods on purpose. > We want to be very careful in how we expose such APIs so as to not get > stuff for future extensions and internal changes. Our current > recommendation is you simply copy/paste the code you need inside your > app. > > On Mon, Jul 19, 2010 at 10:44 PM, Qberticus <[email protected]> wrote: > > I'm wondering if AbsListView and AbsSpinner were intended to be > > extended by non-framework classes. As they are currently implemented > > it is not possible to extend them do to necessary member fields being > > at the package level and also various abstract methods being at the > > package level. However, the documentation as it is currently written > > leads one to believe that it is possible to extend and use these > > classes to implement custom views. > > > > This dissonance between the code and the documentation is confusing. > > I'm going to assume that the main intention of these classes is > > specified in the code and conclude that you cannot and should not > > extend these classes. > > > > I know it's more than likely not possible for the 2.x tree but are > > there any future plans to overhaul these classes so that they will be > > properly extendable? > > > > -- Q > > > > -- > > 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]<android-developers%[email protected]> > > For more options, visit this group at > > http://groups.google.com/group/android-developers?hl=en > > > > > > -- > Romain Guy > Android framework engineer > [email protected] > > 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 [email protected] > To unsubscribe from this group, send email to > [email protected]<android-developers%[email protected]> > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en > -- 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
