I was watching the Google IO videos and Romain mentioned quite quickly
something about the top-level FrameLayout being needed by the OS? That
is the one directly below the getDecorView().

Can I get a more extended explanation of why it is needed? It is not
locked in anyway, we are quite able to remove it, if it was that
critical I would assume it would come already built-in to the
decorView itself, why is it only added as a public subview? I would of
thought the point of the decorView was to handle OS related items,
such as the soft keyboard.

I have not seen any adverse effects to its removal, so I'm fairly
curious to know what it does? I can see clearly what it does with a
title bar but without one, I do not.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to