Bug 397420 - In cocoa, the KeyDown Event and KeyRelease Event of Combo can't be received sometimes.
Summary: In cocoa, the KeyDown Event and KeyRelease Event of Combo can't be received ...
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.7.2   Edit
Hardware: PC Mac OS X
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Lakshmi P Shanmugam CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords: ui
Depends on:
Blocks:
 
Reported: 2013-01-04 03:00 EST by Tony Chan CLA
Modified: 2020-07-30 11:59 EDT (History)
2 users (show)

See Also:


Attachments
patch (955 bytes, patch)
2013-01-15 07:43 EST, Lakshmi P Shanmugam CLA
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Tony Chan CLA 2013-01-04 03:00:21 EST

    
Comment 1 Tony Chan CLA 2013-01-04 03:20:55 EST
In cocoa, when you add the listeners about keys to the combo, you'll find the keydown & keypress event won't always be received.
Here is the example.
First, you should add a selection listener and the key listeners to the combo, add some print segments to trace these listeners.
Then, click mouse to expand the combo, and press Up/Down key to choose the text you want to. Press enter key.
You'll find only keyrelease event can be received at this moment!
Then, press enter key again. The keydown ,keypress and keyrelease event can be received.
Through my test, instead, on win & linux, the key listeners can work well.
Comment 2 Lakshmi P Shanmugam CLA 2013-01-15 07:43:41 EST
Created attachment 225628 [details]
patch

Patch sends the keydown event for enter key, in the same way as its sent for arrow-up/down keys.
Comment 3 Silenio Quarti CLA 2013-01-15 12:41:26 EST
Patch is good.
Comment 4 Eclipse Genie CLA 2020-07-30 11:59:34 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. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. 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.

--
The automated Eclipse Genie.