Having read http://android-developers.blogspot.com/2009/04/future-proofing-your-apps.htm l I noted this little section;
"Due to changes in the View rendering infrastructure, unreasonably deep (more than 10 or so) or broad (more than 30 total) View hierarchies in layouts are now likely to cause crashes. This was always a risk for excessively complex layouts, but you can think of Android 1.5 as being better than 1.1 at exposing this problem..." Will the SDK warn us when we're reaching the limit for crashes? And more to the point why does it crash and not return some form of meaningful error to the app? With an error code or thrown exception developers could create various levels of layout complexity and step down the layout complexity level until they find one the device will support. Al. P.S. No matter what the post says I see this as a regression in functionality and I definitely do not see it as "Android 1.5 as being better than 1.1" in any way. --- * Written an Android App? - List it at http://andappstore.com/ * ====== Funky Android Limited is registered in England & Wales with the company number 6741909. The registered head office is Kemp House, 152-160 City Road, London, EC1V 2NX, UK. The views expressed in this email are those of the author and not necessarily those of Funky Android Limited, it's associates, or it's subsidiaries. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
