They are radio buttons because I want to remember and show the user's last navigation path through the hierarchy. 90% of the time, the user wants to navigate back to the same document. Making them go through 3 levels each time is really tedious. The way I have it, they can go directly to the right tab and get the currently selected document. Remember, there are 1000 documents in the online database and each level of navigation has 5 to 15 choices.
I agree, the long click thing is not obvious at all. But an extra button is also annoying for the power users. I'm leaning towards a Toast message like "Press and hold a button to view document". That brings up another idea. Maybe I can have a "Beginner Mode" in the preferences and show other helpful Toast messages as the user goes through the use cases. The app's not that complex but the simpler I can make it, the better. On Oct 11, 9:50 am, TreKing <[email protected]> wrote: > > If I understand you correctly and you have a list of radio buttons and the > idea is to open the document that corresponds to the selected radio button, > I'd probably scrap the radio button completely and make them buttons and > clicking the item opens the new view. Unless you have another reason for > having them as radio buttons? > > ------------------------------------------------------------------------------------------------- > TreKing <http://sites.google.com/site/rezmobileapps/treking> - Chicago > transit tracking app for Android-powered devices -- 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
