| Summary: | [Key Bindings] "Ctrl+Space" lost to code assist | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Darin Wright <darin.eclipse> |
| Component: | UI | Assignee: | Douglas Pollock <douglas.pollock> |
| Status: | VERIFIED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | hudsonr, kai-uwe_maetzel |
| Version: | 2.0 | Keywords: | accessibility |
| Target Milestone: | 3.0 M9 | ||
| Hardware: | PC | ||
| OS: | Windows 2000 | ||
| Whiteboard: | |||
| Bug Depends on: | 29452 | ||
| Bug Blocks: | |||
|
Description
Darin Wright
Adding Kai as CC The problem is that the editor contributions are kept when activating a different view. So Ctrl+Space is still in the edit menu but disabled. If all editors are closed it works correctly Nick any comments on this. IMO we should do anything for 2.0 since Ctrl+Space is the well known short cut for code assist. The only thing we could do is clear the accelerator when the item is disabled. This is too scary for 2.0 though. *** Bug 23738 has been marked as a duplicate of this bug. *** fixed in tomorrow's integration build. ps. i have noticed on my machine that sometimes using Ctrl+Up and Ctrl+Down you don't see the focus rectangle. this is an SWT problem - the cursor is still moving and you can select with Ctrl+Space This problem is back in M6. I can't reproduce the bug you're describing, but I can reproduce a similar bug. Is it perhaps that "Ctrl+Down" and "Ctrl+Up" does not work in the "Package Explorer" view when a Java editor is open *and* you are using the key configuration called "Standard (3.0) - NEW!"? (that was quite a sentence). If not, could you please give more verbose steps to reproduce? Randy: Steps to reproduce? See bug 52957. In fact, the problems stated in that bug include everything here, but recognizing a regression is an indicator that a JUnit is needed. No steps to reproduce. Moving this bug back to fixed. Verified (I200405190010, Solaris 8, CDE, Motif) |