Bug 32189 - [KeyBindings] preference page: Provide clues that handlers are bound to particular components
Summary: [KeyBindings] preference page: Provide clues that handlers are bound to parti...
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 2.1   Edit
Hardware: All All
: P5 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2003-02-18 17:44 EST by Colin Sampaleanu CLA
Modified: 2019-09-06 16:04 EDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Colin Sampaleanu CLA 2003-02-18 17:44:36 EST
There is a keybinding called 'Synchronize all with CVS' which has no key
assignment by default. It appears that when this binding is assigned to a key,
it only works when you are in a CVS perspective. This would be a lot more useful
if I could use it in the Java perspective, where I would use it so I don't have
to mouse over to the package view and use the right click team menu to do a
synchronize. It is ob no use at all to me in the CVS perspective...
Comment 1 Kevin McGuire CLA 2003-02-21 17:29:14 EST
It not having a key by default is by design.  I thought it was to work 
everywhere though (but maybe that's me just being hopeful :> ).
Comment 2 Colin Sampaleanu CLA 2003-02-21 18:11:20 EST
Does not seem to, unless there is something weird about my system (running M5).
The binding only works in the CVS perspective...
Comment 3 Michael Valenta CLA 2003-02-21 21:38:40 EST
The problem is that the CVS action set is only active by default in the CVS 
perspective. It must be explicitly enabled in other perspectives for the 
actions to be used. This can be done in the Window/Customize Perspective menu 
option (The CVS actions are in the "Other" category.

We should consider moving this bug to UI since it is not obvious that the 
action set is disabled when the keybinding is set.
Comment 4 Colin Sampaleanu CLA 2003-02-21 21:55:49 EST
Thank you for the info.   At a minimum it needs to be in the help, but I think
people will probably still be tripped up by it. It almost needs to be mentioned
in the key binding dialog if there is enough room...
 
Comment 5 Jean-Michel Lemieux CLA 2003-02-25 14:20:22 EST
I agree that this should be moved to UI. It took me a long while to figure that
action set enablement was coupled with keybinding.
Comment 6 Michael Valenta CLA 2003-02-25 14:34:31 EST
Moving to UI. 

To summarize, the issue is that keybindings can be applied to action sets that 
are not active or only active in certain perspectives. It is not obvious in the 
dialog that the action set needs to be activated. 
Comment 7 Nick Edgar CLA 2003-03-03 14:21:14 EST
Agree this is confusing.  Chris, any suggestions?
Comment 8 Chris McLaren CLA 2003-03-03 14:26:31 EST
i'll have a look a this and get back to you.
Comment 9 Nick Edgar CLA 2003-07-02 12:51:00 EDT
This behaviour is admittedly confusing.  There should be some cue in the key 
bindings dialog that the setting will not take effect until the action set is 
made visible.
Comment 10 Douglas Pollock CLA 2003-12-02 15:23:37 EST
Chris: I believe you still wanted to hold on to the keys preference page
redesign work.  This would be part of that.
Comment 11 Douglas Pollock CLA 2004-10-20 21:30:22 EDT
Taking all of Chris' [KeyBindings] bugs. 
Comment 12 Michael Van Meekeren CLA 2006-04-21 13:14:38 EDT
Moving Dougs bugs
Comment 13 Paul Webster CLA 2006-09-28 10:58:38 EDT
There are currently no plans to work on this feature.

PW
Comment 14 Denis Roy CLA 2007-06-22 09:32:29 EDT
Changes requested on bug 193523
Comment 15 Eclipse Webmaster CLA 2019-09-06 16:04:49 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.