[android-developers] Re: Touch mode again (CRUD application context).

2009-01-28 Thread Peli
> (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). If those actions are equally important, what about having a dialog pop up with the different actions when you click on an item (instead of going to 'edit')? (

[android-developers] Re: Touch mode again (CRUD application context).

2009-01-28 Thread Andriy Zakharchuk
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 tha

[android-developers] Re: Touch mode again (CRUD application context).

2009-01-28 Thread Romain Guy
Hi, Like Peli and Mark said, the preferred way to perform contextual actions with Android is to use a long press associated with a context menu. There are examples of this in various sample apps, including code.google.com/p/apps-for-android or code.google.com/p/shelves. Another way to do it, but

[android-developers] Re: Touch mode again (CRUD application context).

2009-01-28 Thread Peli
Android also supports lng-click, which is what you need. (see the Notepad example). Peli www.openintents.org On Jan 28, 5:29 pm, Andriy Zakharchuk wrote: > Hello all, > > I have a question about touch mode (probably it was already asked, > sorry if so, but I couldn't find a discussion l

[android-developers] Re: Touch mode again (CRUD application context).

2009-01-28 Thread Mark Murphy
Andriy Zakharchuk wrote: > I tried to implement it in a traditional way (the approach I described > first). So I created a list screen, put 'Add', 'Edit', 'Delete' > commands into menu. I couldn't get Edit and Delete menu commands > working in touch mode, because I couldn't obtain selected item.