addFocusables was on the wrong track. The solution was much more mundane.
My custom component was derived from View. It needed to be derived from one of the ViewGroup classes - in my case FrameLayout. Nigel On Sep 3, 8:35 pm, Nigel <[email protected]> wrote: > I'm creating a custom component. The child components are not acting > as expected in regard to my custom components re-acting with its > siblings. > > On investigations to solve this I came across View.addFocusables and > View.addTouchables. These may help me, but I'm not really sure how > they're intended to be used. Can anyone provide a better description, > or example, of how these are intended to be used? A dig around on > Google revealed nothing :-(... > > Any explanation - or links to pages I couldn't find - much > appreciated. > > Cheers -Nigel --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
