Community
Participate
Working Groups
If I edit a scrapbook.jpage in the Java EE perspective the keybindings Ctrl+Shift+D, Ctrl+Shift+I and Ctrl+U no longer works. However if I select the expression, right-click on it and select Display, Inspect or Execute then it works. If I switch perspective to Java then the key bindings works as they should.
Are you in Indigo? Or Juno? Please attach anything in your .log file, <workspace>/.metadata/.log PW
(In reply to comment #1) > Are you in Indigo? Or Juno? > > Please attach anything in your .log file, <workspace>/.metadata/.log > > PW I'm using Indigo. This error doesn't produce any entry in my .log file, so I don't think there is any need for attaching it. When I for example mark and press Ctrl+U for following expression in scrapbook.jpage String s = "test"; System.out.println("s = " + s); nothing happens, no error, nothing at all. But if I right click on the expression and select Execute from there then it works, as intended. Described scenario occurres in the Java EE perspective. On the other hand, if switch perspective to the Java view then the key binding works as they should. So it seems to be a small bug somewhere.
(In reply to comment #2) > > This error doesn't produce any entry in my .log file, so I don't think there > is any need for attaching it. So there are no errors in your error log? (In reply to comment #0) > If I edit a scrapbook.jpage in the Java EE perspective the keybindings > Ctrl+Shift+D, Ctrl+Shift+I and Ctrl+U no longer works. When did they work in the Java EE perspective, that they no longer work now? PW
> (In reply to comment #2) > > > > This error doesn't produce any entry in my .log file, so I don't think there > > is any need for attaching it. > > So there are no errors in your error log? No errors related to this bug exists in the log. > > (In reply to comment #0) > > If I edit a scrapbook.jpage in the Java EE perspective the keybindings > > Ctrl+Shift+D, Ctrl+Shift+I and Ctrl+U no longer works. > > When did they work in the Java EE perspective, that they no longer work now? They never worked in Java EE perspective, the key bindings only works in Java perspective. > > PW
(In reply to comment #4) > > No errors related to this bug exists in the log. If there are any errors, please attach them. > They never worked in Java EE perspective, the key bindings only works in > Java perspective. This is most like related to keybindings backed by actionSets. If the actionSet is active in the Java perspective but not in the java EE perspective, then the keybinding won't work. Can you see a Command Group in CustomizePerspective>Command Groups that shows the 3 actions you mentioned? PW
Created attachment 231128 [details] Log file
(In reply to comment #5) > (In reply to comment #4) > > > > No errors related to this bug exists in the log. > > If there are any errors, please attach them. I attached the log file now. > > > They never worked in Java EE perspective, the key bindings only works in > > Java perspective. > > This is most like related to keybindings backed by actionSets. If the > actionSet is active in the Java perspective but not in the java EE > perspective, then the keybinding won't work. > > Can you see a Command Group in CustomizePerspective>Command Groups that > shows the 3 actions you mentioned? Yes I can see the actions there. > > PW
(In reply to comment #7) > > Can you see a Command Group in CustomizePerspective>Command Groups that > > shows the 3 actions you mentioned? > > Yes I can see the actions there. If you open the Customize Perspective Dialog in the Java EE perspective is that command group selected? PW
(In reply to comment #8) > (In reply to comment #7) > > > Can you see a Command Group in CustomizePerspective>Command Groups that > > > shows the 3 actions you mentioned? > > > > Yes I can see the actions there. > > If you open the Customize Perspective Dialog in the Java EE perspective is > that command group selected? > > PW I feel kind of dumb right now... You're correct, the command groups availability was indeed unselected. Directly after selecting that command groups availability the key binding works as they should. So we can close this case.
(I only knew that because it happened to me :-) Thanks for pursuing this. PW
When you open the context menu, the MOD1+U keybinding is displayed there regardless of whether the "Java debug" action set is enabled in the current perspective. This is misleading, since the keybinding doesn't work at all. There is no reason why the user should be forced to show the "Execute" action all the time. The scrapbook editor should dynamically register the action, just like it does for "Quick Fix".
