Thank you very much for answers!

I've seen discussions about view hierarchy depth, but after finding
out that StackOverflow pops-up exclusively at the moment of text
wrapping I didn't believed this is the case.

Hierarchyviewer revealed that my hierarchy is really deep (14), but
it's not as messy - the biggest portion of this depth is added by
TabActivity. As I found out, similar problem is being solved here:
http://groups.google.com/group/android-developers/browse_thread/thread/277e81c07591219f/f3f0b6f6ac529bcb

I did some hotfix to prevent text wrapping and now I can think about
reducing the depth (I don't see a way to do it right now, without
rewriting whole UI, but hopefully I'll find something ;).

Thanks again,
  Mike


On May 6, 5:38 pm, Romain Guy <[email protected]> wrote:
> > How deep and complicated is your view hierarchy? With Android 1.5, I get
> > the sense that StackOverflowError will be triggered by a too-complex set
> > of views, particularly in terms of depth. You can use hierarchyviewer
> > (in the tools/ of your SDK) to see how many layers you have -- if you're
> > in double digits on the deepest branch, you might need to find ways to
> > simplify the UI.
>
> It was already the case in 1.0 and 1.1 but because of new features
> added in Cupcake, StackOverflowException now happen a bit earlier.
> This means that the app was almost overflowing anyway.
>
> --
> 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]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to