Thank you for comments, guys. Probably, I was not clear, but I'm still using context menus. However, in my opinion, context menu is a secondary way to perform an action. So, there should always be a primary way (options menu, item click, toolbar button). Context menu is less obvious/intuitive than other controls. It's OK for geeks (or guys who read documentation :)), but not for typical users. Thus I think that context menus can be used only as secondary shortcuts.
Do you think it's OK to provide some functions only via context menu without alternative? Doesn't it make the application unclear, more difficult to learn (at least when other applications in the system, and other screens in this application have this alternative)? > The menu, the one that comes up when one presses the menu key, is > meant for global actions only, actions that affect the entire > activity. I understand this, I agree with it and that's why I'm asking the question. All standard Android applications are using this approach. I'd like my application to be consistent with them, and it looks mostly cool... except one screen which discomforts me (I have 5 entities to be stored in the database and only one of them has only one attribute and any actions can be performed on it). --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
