Community
Participate
Working Groups
Navigation shortcuts (alt + left/right on Windows) no longer works. I'm aware of bug 150087 but I decided to open a new one because that one affects Mac and I'm on Windows. If using the toolbar buttons, navigation works properly. Bug demonstration / installed plugins: https://youtu.be/hiPar48kRWM
Can't reproduce with 4.16 RC2. Any errors in the log? How did you get into this state?
(In reply to Andrey Loskutov from comment #1) > Can't reproduce with 4.16 RC2. Any errors in the log? How did you get into > this state? Clearing the error log and performing the Alt + Left hotkey, nothing shows on error log. Before clearing, some erros occurred. If needed, I can post them. To get into this state, I basically open and start using Eclipse (I don't know if I usually do something that breaks something, though).
Created attachment 283209 [details] Log
The following log entry calls my attention: !ENTRY org.eclipse.jface 2 0 2020-06-09 18:19:27.184 !MESSAGE Keybinding conflicts occurred. They may interfere with normal accelerator operation. !SUBENTRY 1 org.eclipse.jface 2 0 2020-06-09 18:19:27.184 !MESSAGE A conflict occurred for CTRL+SHIFT+V: Binding(CTRL+SHIFT+V, ParameterizedCommand(Command(org.jkiss.dbeaver.core.edit.paste.special,Colar Avançado, Colar com configurações especiais, Category(org.jkiss.dbeaver.core.util,Utilitário,Utilitário de comando,true), org.eclipse.ui.internal.WorkbenchHandlerServiceHandler@3c0becae, ,,true),null), org.eclipse.ui.defaultAcceleratorConfiguration, org.eclipse.ui.contexts.window,,,system) Binding(CTRL+SHIFT+V, ParameterizedCommand(Command(org.eclipse.jdt.debug.ui.command.OpenFromClipboard,Open from Clipboard, Opens a Java element or a Java stack trace from clipboard, Category(org.eclipse.ui.category.navigate,Navigate,null,true), org.eclipse.ui.internal.WorkbenchHandlerServiceHandler@373c367, ,,true),null), org.eclipse.ui.defaultAcceleratorConfiguration, org.eclipse.ui.contexts.window,,,system) !SUBENTRY 1 org.eclipse.jface 2 0 2020-06-09 18:19:27.184 !MESSAGE A conflict occurred for CTRL+SHIFT+A: Binding(CTRL+SHIFT+A, ParameterizedCommand(Command(org.jkiss.dbeaver.core.navigator.set.default,Definir com padrão, Definir como objeto padrão, Category(org.jkiss.dbeaver.core.navigator,Navegador de Banco de Dados,Comandos do Navegador de Banco de Dados,true), org.eclipse.ui.internal.WorkbenchHandlerServiceHandler@79690a0a, ,,true),null), org.eclipse.ui.defaultAcceleratorConfiguration, org.eclipse.ui.contexts.window,,,system) Binding(CTRL+SHIFT+A, ParameterizedCommand(Command(org.eclipse.pde.ui.openPluginArtifact,Open Plug-in Artifact, Open a plug-in artifact in the manifest editor, Category(org.eclipse.ui.category.navigate,Navigate,null,true), org.eclipse.ui.internal.WorkbenchHandlerServiceHandler@619944a7, ,,true),null), org.eclipse.ui.defaultAcceleratorConfiguration, org.eclipse.ui.contexts.window,,,system) After I saw that, I removed CTRL+SHIFT+(A|V) mappings and restarted Eclipse. The error log (as expected) disappeared. But ALT+LEFT still doesn't work.
The bug happening: https://youtu.be/yl9xYTs-2BQ Please, note that when I use tool bar buttons, the navigation works properly.
I was able to reproduce it for a while, on a 4.17 I build. The keys don't work just after restart. It appeared to me that the navigation started working by keys after using the menu items, or after switching tabs. However, I could no longer investigate because it doesn't appear anymore. Can you confirm that the keys start working after using the toolbar buttons or switching tabs? Seems that there is a race condition somewhere.
(In reply to Rolf Theunissen from comment #6) > I was able to reproduce it for a while, on a 4.17 I build. The keys don't > work just after restart. It appeared to me that the navigation started > working by keys after using the menu items, or after switching tabs. > However, I could no longer investigate because it doesn't appear anymore. > > Can you confirm that the keys start working after using the toolbar buttons > or switching tabs? > > Seems that there is a race condition somewhere. It makes no difference. Still doesn't work.
One more information: if I go to keys configuration, remove and re-add the binding, the shortcut starts working (until the next Eclipse restart).
I have similar problems. I also use dbeaver plugin. Now even the CTRL+F11 (run) shortcut doesn't work anymore. I recognized, when I start eclipse without a dbeaver-data-view opened, the shortcuts are working. But when I once display a dbeaver-data-view, after that, the shortcuts do not work anymore, even when I switch to a java-file-editor. Is this an eclipse bug or a dbeaver bug?
I am using eclipse Version: 2021-12 (4.22.0) Build id: 20211202-1639
(In reply to jfc jrtc from comment #9) > I have similar problems. I also use dbeaver plugin. > > Now even the CTRL+F11 (run) shortcut doesn't work anymore. > > I recognized, when I start eclipse without a dbeaver-data-view opened, the > shortcuts are working. > > But when I once display a dbeaver-data-view, after that, the shortcuts do > not work anymore, even when I switch to a java-file-editor. > > Is this an eclipse bug or a dbeaver bug? DBeaver defines its own shortcuts bound to CTRL+F11, see [1]. So there is a conflict in bindings. Did this work on older versions? There might have been a change in priority of handlers. [1] https://dbeaver.com/docs/wiki/Shortcuts/
Maybe it's a conflict, but then, at least, after switching to a java-editor, the window-wide shortcut should work. I have also the same problems with alt+left/right shortcuts. I think the CTRL-F11 problem is new, the other problem is since 1-2 years at least.
I now removed the other ctrl-f11 shortcut, and it works, so thanks for your hint about the dbeaver shortcut. Is there now a priority of handlers bug to be fixed?
(In reply to jfc jrtc from comment #13) > I now removed the other ctrl-f11 shortcut, and it works, so thanks for your > hint about the dbeaver shortcut. Is there now a priority of handlers bug to > be fixed? I expect that the ctrl-f11 regression is around since 4.16, this is a regression/stricter behavior in Eclipse see Bug 571513 Comment 6. But that is long ago also. If it is a recent regression, it could be caused by changes in DBeaver too. Probably this should be fixed in DBeaver. What was the latest version that it did work?
(In reply to Rolf Theunissen from comment #14) > (In reply to jfc jrtc from comment #13) > > I now removed the other ctrl-f11 shortcut, and it works, so thanks for your > > hint about the dbeaver shortcut. Is there now a priority of handlers bug to > > be fixed? > > I expect that the ctrl-f11 regression is around since 4.16, this is a > regression/stricter behavior in Eclipse see Bug 571513 Comment 6. But that > is long ago also. If it is a recent regression, it could be caused by > changes in DBeaver too. Probably this should be fixed in DBeaver. > What was the latest version that it did work? DBeaver change/issue that should have fixed the conflict: https://github.com/dbeaver/dbeaver/issues/10809
