Bug 193332

Summary: [KeyBindings] Keybinding conflicts occurred for Ctrl+W and Ctrl+F4 with views switcher
Product: [Eclipse Project] Platform Reporter: Markus Keller <markus.kell.r>
Component: UIAssignee: Platform UI Triaged <platform-ui-triaged>
Status: ASSIGNED --- QA Contact:
Severity: normal    
Priority: P3 CC: daniel_megert
Version: 3.3   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard:

Description Markus Keller CLA 2007-06-19 11:04:06 EDT
I20070615-1200

- new workspace
- do these 3 steps quickly (can't reproduce if too slow)
    - press Ctrl and hold down
    - press and release F7
    - click into the Welcome background

-> Log:
!ENTRY org.eclipse.jface 2 0 2007-06-19 17:01:18.234
!MESSAGE Keybinding conflicts occurred.  They may interfere with normal accelerator operation.
!SUBENTRY 1 org.eclipse.jface 2 0 2007-06-19 17:01:18.234
!MESSAGE A conflict occurred for CTRL+W:
Binding(CTRL+W,
        ParameterizedCommand(Command(org.eclipse.help.ui.closeTray,Close User Assistance Tray,
                Close the user assistance tray containing context help information and cheat sheets.,
                Category(org.eclipse.ui.category.help,Help,null,true),
                org.eclipse.help.ui.internal.CloseHelpTrayHandler,
                ,,true),null),
        org.eclipse.ui.defaultAcceleratorConfiguration,
        org.eclipse.ui.contexts.dialog,,,system)
Binding(CTRL+W,
        ParameterizedCommand(Command(org.eclipse.ui.file.close,Close,
                Close the active editor,
                Category(org.eclipse.ui.category.file,File,null,true),
                org.eclipse.ui.internal.CloseEditorHandler,
                ,,true),null),
        org.eclipse.ui.defaultAcceleratorConfiguration,
        org.eclipse.ui.contexts.window,,,system)
!SUBENTRY 1 org.eclipse.jface 2 0 2007-06-19 17:01:18.234
!MESSAGE A conflict occurred for CTRL+F4:
Binding(CTRL+F4,
        ParameterizedCommand(Command(org.eclipse.help.ui.closeTray,Close User Assistance Tray,
                Close the user assistance tray containing context help information and cheat sheets.,
                Category(org.eclipse.ui.category.help,Help,null,true),
                org.eclipse.help.ui.internal.CloseHelpTrayHandler,
                ,,true),null),
        org.eclipse.ui.defaultAcceleratorConfiguration,
        org.eclipse.ui.contexts.dialog,,,system)
Binding(CTRL+F4,
        ParameterizedCommand(Command(org.eclipse.ui.file.close,Close,
                Close the active editor,
                Category(org.eclipse.ui.category.file,File,null,true),
                org.eclipse.ui.internal.CloseEditorHandler,
                ,,true),null),
        org.eclipse.ui.defaultAcceleratorConfiguration,
        org.eclipse.ui.contexts.window,,,system)
Comment 1 Mark A. Ziesemer CLA 2007-06-20 14:43:06 EDT
I've not yet upgraded to the latest RC.  Getting same errors under I20070503-1400.

Note that I don't need to follow the same steps to reproduce.  Notably, I'm sure I didn't use F7.

Thinking maybe the error is an error itself.  Both CTRL+W and CTRL+F4 are defaulted to both "Close" and "Close User Assistance Tray".  However, the 1st is set for "When" = "In Windows", and the 2nd for "In Dialogs".  Since being focused in a dialog should prevent key bindings from affecting the background window, I don't see how this should be an issue.
Comment 2 Markus Keller CLA 2007-06-21 04:17:24 EDT
(In reply to comment #1)
Mark: we made quite a few fixes in this area after I20070503-1400. Please file a new bug if you see such messages in different scenarios in I20070615-1200 or later.

AFAIK, the only open issues at this time are this bug and bug 185523.
Comment 3 Mark A. Ziesemer CLA 2007-06-25 13:07:21 EDT
Agreed.  Error not appearing without attempting described steps under RC4.  Sorry for the mislead...
Comment 4 Eclipse Webmaster CLA 2019-09-06 16:18:20 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.