Thanks for your reply Mark. I realise that the best solution is to collapse the hierarchy, however I am still interested to know the cause.
On Dec 30, 9:04 am, Mark Murphy <[email protected]> wrote: > thesquib wrote: > > I just wanted to add that I am interested in finding a way around > > this, or just to find out if it is a limitation which will not go > > away. > > I'd focus instead on getting rid of 20+ classes in the hierarchy. > > -- > Mark Murphy (a Commons Guy)http://commonsware.com > > Android Training on the Ranch! -- Mar 16-20, > 2009http://www.bignerdranch.com/schedule.shtml --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
