Bug 234285 - Add SWT.MENU key constant (KeyDown/KeyUp).
Summary: Add SWT.MENU key constant (KeyDown/KeyUp).
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.4   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Steve Northover CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-05-27 20:59 EDT by Paul Slauenwhite CLA
Modified: 2019-09-06 16:06 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Paul Slauenwhite CLA 2008-05-27 20:59:30 EDT 
Menu key event not received by listener (KeyDown/KeyUp).

When the menu key (between the right Alt (or right Windows key) and right Ctrl buttons (see http://en.wikipedia.org/wiki/Menu_key) is pressed/released, the event is not received by org.eclipse.swt.events.KeyListener or org.eclipse.swt.widgets.Listener (KeyDown/KeyUp).

Steps to reproduce:

1) Run http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.swt.snippets/src/org/eclipse/swt/snippets/Snippet25.java?view=co.
2) Press the  menu key (between the right Alt (or right Windows key) and right Ctrl buttons (see http://en.wikipedia.org/wiki/Menu_key).
3) Note the missing key pressed/released events.
Comment 1 Bogdan Gheorghe CLA 2008-05-28 11:58:03 EDT 
This is really a feature request to add a Menu key constant (which we don't have in SWT at the moment).

Note that you can determine when the menu detect key is pressed by listening for MenuDetect: 

shell.addListener(SWT.MenuDetect, new Listener () { etc.

or

shell.addMenuDetectListener( etc.
Comment 2 Eclipse Webmaster CLA 2019-09-06 16:06:11 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.