10-03-2012 08:25 PM
I have a screen with several dropdowns on it. For the ones that are near the bottom of the screen it seems impossible to actually reach and select all the options when the app is running.
I'm wondering: Is this a bug in Cascades or is there a specific workaround for this that I don't know about?
10-04-2012 12:40 AM
I would try updating the UI for this type of scenario. Detect if the user is on the dropdown at the bottom of the screen...then change visibility or translationX or translationY on components above tat drop down. This will shift the dropdown to the upper portion of the screen making for a great UX.
That's how I would do it. Think about what is relevant to the user at any given point in their interaction with your app and respond accordingly.
Do people really want their phone making decisions for them? Whatever happened to the human element? Stop this madness!
10-04-2012 01:18 AM
I suppose I could. But: shouldn't the framework itself take care of this scenario?
On Playbook, a dropdown would automatically open upwards in this scenario for example...
That's why I figured this may be a bug rather than something we're supposed to deal with ourselves in our code.
10-04-2012 02:13 AM
For now I have decided to have these screens be in portrait mode which effectively cures the problem. It's not ideal because the main screen of this app is actually landscape only but at least now I'm effectively avoiding the issue.
But yes, I also think the framework should deal with this by itself in an elegant way. Like on PlayBook for example.
10-14-2012 06:31 PM
10-24-2012 01:55 AM
I dnt have this issue in Beta 3... As someone suggested above if you put all DropDowns and other screen elements into ScrollView the framework will scroll up/down and always ensure the expanded DropDown is in view. At least this is how it workd for me.
01-20-2013 06:26 PM