On Apr 24, 5:00 pm, Mark Murphy <[email protected]> wrote: > On Sun, Apr 24, 2011 at 7:49 PM, Keith Wiley <[email protected]> wrote: > > ...and to wrap up the philosophical argument that this thread > > unintentionally flared, I really don't see why double or triple tap > > long presses should be expected to exhibit redundant behavior with > > that of single tap long presses. > > That seems reasonable. Your opening line of the thread ("I want to > intercept an EditText long-press and do something with it other than > present a contextual menu") didn't explain that,
I admit, I did not qualify my question with much backround. > BTW, just so I'm on the right page: a double-tap long-press would be > tap + long-press? And triple-tap long-press is tap + tap + long-press? Yes, precisely. Double-tap long-press in my lingo is down-up-dooown. Triple is down-up-down-up-dooown. I used similar actions for a different app almost a year and a half ago (WildSpectra) but they weren't on an EditText, they were just on a custom view, so the context menu issue never came up before. Regarding the actual solution, unless I have mistaken what I am seeing, it does look like my solution works: override showContextMenu(). Cheers! -- 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
