If you absolutely need to access those fields/methods you CAN use Java reflection, but it's a very fragile solution in that those fields could change across Android iterations. Using reflection you can change the visibility of the private fields/methods and invoke them/ change their values. Here's an example, which also discusses the dangers:
http://radio.javaranch.com/val/2004/05/18/1084891793000.html The alternative would be to copy the code from that class and create your own, making those fields protected or providing methods to mutate them. Jonathan On Mar 21, 1:46 pm, Justin Anderson <magouyaw...@gmail.com> wrote: > You can only change the behavior of public or protected > methods/variables... Private scope means private to everybody... including > sub-classes. > > Standard OOP design... > > Thanks, > Justin Anderson > MagouyaWare Developerhttp://sites.google.com/site/magouyaware > > > > > > > > On Mon, Mar 21, 2011 at 2:30 PM, trans <transf...@gmail.com> wrote: > > "non-sense"? I need to change it's behavior. How else am I going to do it? > > > -- > > 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 -- 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
