Summary: | New copy line feature doesn't work for me | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | John Arthorne <john.arthorne> |
Component: | Text | Assignee: | JDT-Text-Inbox <jdt-text-inbox> |
Status: | RESOLVED INVALID | QA Contact: | |
Severity: | minor | ||
Priority: | P3 | Keywords: | needinfo |
Version: | 3.0 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Windows 2000 | ||
Whiteboard: |
Description
John Arthorne
2003-07-18 10:40:29 EDT
strange... you could always check whether there is a key-binding problem. If the action gets invoked at all, it should come by MoveLinesAction.run(). Otherwise, (you've probably done that already, but just to make sure) check if there are any conflicts in the keybinding preferences. (MoveLinesAction comes in two flavors: moving lines or copying lines...) The event isn't getting through to your action. There must be a problem either in the accelerator processing code or SWT. I suggest moving to platform for further investigation... they can bother me directly for more details. It's not just a matter of conflicting keybindings. I tried it on a new workspace (all default bindings), and it still didn't work. You might want to check if you have any windows tools installed that could consume the keybinding upfront. Ctrl+Alt+... combinations are not unlikely to be used by some window / multimonitor etc. switch feature. What happens if you transfer the keybinding to something else (Ctrl+9 or so) - does it work then? (Key Binding Prefs->Text Editing->Copy Lines / Duplicate Lines) Yes, it works with another keybinding (I used Ctrl+Alt+9). I just have a pretty standard windows install, I can't think of anything... I'll play around with it a bit more. I suspect it is something similar to that bug. I still cannot assign Ctrl+Alt+Down to any command, and it doesn't work for copy line. I agree with the theory that Windows or some driver is stealing the key binding, although it doesn't have any effect when I press it. I am running an IBM PC (not Dell as in bug 71539)... if this is common it might be worth choosing a different default binding (if you can find one ;) Otherwise, ok to close. Setting to REMIND until we have more data Get rid of deprecated state. . |