Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 343300

Summary: Support gesture for context menu
Product: [RT] RAP Reporter: Austin Riddle <austin.riddle>
Component: RWTAssignee: Project Inbox <rap-inbox>
Status: NEW --- QA Contact:
Severity: normal    
Priority: P3 CC: stephan.leichtvogt, tbuschto
Version: 1.4   
Target Milestone: ---   
Hardware: PC   
OS: All   
Whiteboard:
Bug Depends on:    
Bug Blocks: 394180, 323032    
Attachments:
Description Flags
Simple implementation of content-menu support in iPad
none
Updated Patch from Austin Riddle none

Description Austin Riddle CLA 2011-04-19 14:17:14 EDT
We need to support a gesture for opening the context menu.

This first-attempt patch uses the double finger tap as recommended here:

http://itap-mobile.com/itap-rdp/manual#importantgestures

to support the context menu.
Comment 1 Austin Riddle CLA 2011-04-19 14:18:32 EDT
Created attachment 193612 [details]
Simple implementation of content-menu support in iPad
Comment 2 Tim Buschtoens CLA 2011-04-20 04:35:57 EDT
Hm. On android the pattern is to use one finger and hold for about a second. I'm currently uncertain which to support. I guess we could also support both. 

This is complicated in so far that one has to make sure it works in all combinations, especially with left-button mouseevents. E.g. what if one of the two finger is slightly faster than the second? (So you have 0-1-2-1-0). What if the two finer hit different targets? What if you move them slightly, which would be detected as a pinch-zoom by the ipad?
Comment 3 Stephan Leicht Vogt CLA 2011-10-26 04:28:21 EDT
Created attachment 205969 [details]
Updated Patch from Austin Riddle

I updated the patch from Austin Riddle to the current CVS HEAD and tried it on my iPad. Unfortunately nothing happens. No context menu appears on the table. Does this patch need more changes in other code-parts?

I would like to see this issue solved and would contribute with discussion and patches. Until this is solved, we have to write a workaround in java.