Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 29452 - [Key Bindings] Ctrl+Up and Ctrl+Down are blocked from table and tree widgets
Summary: [Key Bindings] Ctrl+Up and Ctrl+Down are blocked from table and tree widgets
Status: RESOLVED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 2.1   Edit
Hardware: PC Windows XP
: P2 major (vote)
Target Milestone: 2.1 RC1   Edit
Assignee: Chris McLaren CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 28749 30893 (view as bug list)
Depends on:
Blocks: 20150
  Show dependency tree
 
Reported: 2003-01-14 11:47 EST by Nick Edgar CLA
Modified: 2003-02-26 15:26 EST (History)
3 users (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 Nick Edgar CLA 2003-01-14 11:47:09 EST 
build I20020307

- start Eclipse
- get several items in the Tasks view (e.g. create several tasks)
- select the first item
- press Ctrl+Down Arrow
- it has no effect (it should move focus to the next item)
- Window > Customize Perspective > Other > uncheck Help > OK
- Ctrl+Down Arrow now works
- Window > Customize Perspective > Other > check Help > OK
- Ctrl+Down Arrow still works

Unchecking Software Updates also fixes the problem, but other action sets do 
not.  I suspect there is a problem with the hidden menu items for accelerators 
that gets fixed up when an action set that affects the Help menu is turned off 
or on.

Ctrl+Up and Ctrl+Down are important for accessibility, allowing you to multi-
select multiple disjoint items (with Ctrl+Space).
Comment 1 Chris McLaren CLA 2003-02-11 14:08:15 EST 
*** Bug 28749 has been marked as a duplicate of this bug. ***
Comment 2 Chris McLaren CLA 2003-02-11 14:13:56 EST 
interesting method to get it to work..
there are two problems here:

a) Kai defines Scroll Up, Scroll Down, and many other text actions in the 
Global Scope, when he should be defining them all in the Text Scope, and 
setting the text scope in his KeyBindingService instance. remove the bindings 
for Ctrl+ARROW_DOWN and Ctrl+ARROW_UP in org.eclipse.ui plugin.xml and things 
work fine.

b) undefining these keys in the key customization does not seem to be 
sufficient to allow the key to pass through to the widgets. this might be 
related to a hidden menu problem as you suggest.

copying kai while i look at problem b). 

ps. As previously discussed, if a user WANTS to redefine Ctrl+Arrow Down, etc. 
they can - even though they may break accessibility for themselves.
Comment 3 Chris McLaren CLA 2003-02-11 14:18:24 EST 
*** Bug 30893 has been marked as a duplicate of this bug. ***
Comment 4 Chris McLaren CLA 2003-02-26 15:26:08 EST 
fixed (in tomorrow's integration build).
keys registered to commands pass through to the widget if the command does not 
have any actions to handle it. 

select away...