On Apr 24, 3:02 pm, Mark Murphy <[email protected]> wrote: > On Sun, Apr 24, 2011 at 5:54 PM, Keith Wiley <[email protected]> wrote: > > I want to intercept an EditText long-press and do something with it > > other than present a contextual menu. > > Please don't. Users will expect the standard EditText context menu to > appear, so they can do silly things like edit the text. Android > developers get ripped to shreds by users and the media for having zero > UI discipline, breaking existing UI patterns and causing no two apps > to work the same -- your proposal is a case in point. > > If your goal is for users to not edit the text, then don't use an EditText. > > If your goal is for users to edit the text, leave the context menu > alone, and find some other way to trigger whatever it is that you are > trying to do.
I understand your point, but you aren't being completely fair. My Edit text can detect not only single also double and triple taps (I had to hack triple tap detection from scratch of course). I want to provide additional functionality on double or triple tap long presses, but it won't work if the contextual menu is forced upon all long presses. Furthermore my app offers a fully configurable UI where single/double/triple taps/long-presses/drags can be assigned to numerous complex functions in a way that greatly empowers the user. So, with all due respect, we can debate the philosophy how to present such UIs in a parallel or separate discussion, but it is tangential to my question of how to technically achieve such powerful goals. Do you know how to do what I'm trying to do? Thank you. -- 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
