Hey Romain, Thanks for the reply,
I can understand why this is not an ideal ui design - I entirely agree. But this doesn't change the fact that there seems to be some regression with the Android UI code. On researching further I've found that there are a number of registered bugs for 2.2 to do with browsers exhibiting similar problems whilst showing pages containing frames. Looks like something fundamental has changed here. As far as our use case goes - I need to be able to display whatever a user requires in their screen. Currently we can show these screens on Windows, iPhone & Blackberry and Android < 2.1 without any issues. But Android 2.2 suddenly has this issue with the nesting. Whilst we *could* design the app to work around this bug by using a popup editor - this does not help us keep things consistent, and your architecture bug free. As a workaround - do you know of any way to reset Nexus ones back to 2.1? Cheers, :) Peter. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Romain Guy Sent: Wednesday, 15 September 2010 4:42 PM To: [email protected] Subject: Re: [android-developers] Scrolling broken in 2.2 ? Hi, You should never have a scrolling widget inside a scrolling widget; for instance a ListView inside a ScrollView. The behavior for such a setup is pretty much guaranteed to not work (and definitely not guaranteed to work.) On Tue, Sep 14, 2010 at 11:39 PM, Peter Carpenter <[email protected]> wrote: > My app builds up a custom screen as dictated to me via the users > 'application'. This means that I can end up in the situation where I have a > parent scrollview and somewhere down the heirachy I can have a listView or a > multiline TextView. > > > > Both of these scenarios continue to work fine under 2.1, however are broken > in 2.2 (both device and emulator). The symptoms are that the child (list or > textview) is unable to scroll using touch gestures although they can be > scrolled using the keypad. > > > > Has anyone else experienced this behaviour and/or have a work around?? It > appears that the onTouchEvent function in View has been changed > substantially but I am currently delving into the code... > > > > Cheers, > > > > Peter. > > -- > 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 -- 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 -- 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
