Context: My app has a list of entries. It uses an ExpandableListView to display the entry date and type as a group, and when you short-press it, it expands to show detailed data on that entry. It also uses a long-click to bring up a context-menu for each entry, from which the user can select some action - "Delete", "Edit" and "Edit Date".
Reading the Android UI guidelines recently, long-press has been changed such that it should be a "selection" action rather than a "display context-menu" action. I'm happy with this - my context menu isn't all that visible.
But I'm not certain how to implement my contextual actions anymore.
These actions wouldn't support multi-select (Delete could, but doesn't have to - I think it would be rare to have to delete multiples), so I'm not certain about the selection contextual action bar. I saw an example that changed the View for the entry to be a Spinner, and you short-press to drop-down the spinner and inside there are actions. Great - it's visible because of the little notch in the bottom-right, and it's single-entry only. Unfortunately, because I'm using an ExpandableListView, doing this means that the child no longer expands!
This section of the app is for viewing data you've already input, and is not the main focus of the app. The actions would be rarely used in relation to the rest of the app, and so do not need more prominence.
The actual question: How would you combine a parent/child relationship (ExpandableListView being one way of doing this), with single-select contextual actions?
A few app screenshots, hopefully that's ok rather than a mockup. The context menu is presently brought up by long-pressing, but I wanted to change to the "new" Android long-press design.