Bug 43805

Summary: [KeyBindings] preference page: Should remember previous selection
Product: [Eclipse Project] Platform Reporter: Nick Edgar <n.a.edgar>
Component: UIAssignee: Platform UI Triaged <platform-ui-triaged>
Status: ASSIGNED --- QA Contact:
Severity: enhancement    
Priority: P5 CC: michaelvanmeekeren
Version: 3.0Keywords: helpwanted
Target Milestone: ---   
Hardware: All   
OS: All   
Whiteboard:

Description Nick Edgar CLA 2003-09-27 22:27:20 EDT
build I20030917

- open Keys pref page
- select some command, e.g. File > Close
- close the dialog, either by making a change or canceling
- open it again
- the selection is lost -- it's showing the first command in the first category

It would be very helpful to have it remember the previous selection, 
particularly in the case where a binding has been added, removed or restored.
This allows the user to exit the prefs, try out the change, then go back for 
more adjustments.

It wouldn't hurt to remember the command category and name on cancel as well, 
although you wouldn't want to remember a change in configuration that was 
canceled.
Comment 1 Douglas Pollock CLA 2004-10-20 21:25:13 EDT
Taking all of Chris' [KeyBindings] bugs. 
Comment 2 Douglas Pollock CLA 2005-02-21 15:18:14 EST
*** Bug 84721 has been marked as a duplicate of this bug. ***
Comment 3 Douglas Pollock CLA 2005-04-12 11:37:02 EDT
The preference page re-work has been pulled for the 3.1 plan to work on performance.
Comment 4 Michael Van Meekeren CLA 2006-04-21 13:14:39 EDT
Moving Dougs bugs
Comment 5 Paul Webster CLA 2006-09-28 10:59:46 EDT
There are currently no plans to work on this feature.

PW
Comment 6 Denis Roy CLA 2007-06-22 09:32:31 EDT
Changes requested on bug 193523
Comment 7 Eclipse Webmaster CLA 2019-09-06 16:08:30 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.