| Summary: | [WorkbenchParts] Global Refactorings disabled after opening editor | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Michael Valenta <Michael.Valenta> |
| Component: | UI | Assignee: | Stefan Xenos <sxenos> |
| Status: | VERIFIED FIXED | QA Contact: | |
| Severity: | critical | ||
| Priority: | P1 | CC: | andre_weinand, douglas.pollock, Mike_Wilson |
| Version: | 3.1 | ||
| Target Milestone: | 3.1 M7 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Michael Valenta
Michael, extract method goes through validateEdit in this case. I tested it with I20050419-1200 and it works for me. Could it be that the file isn't on the build path ? Any additional steps to reprodcue. OK, doing some more testing this looks like a part activation problem. It has nothing to do with read-onyl.The context menu contains all menu entries and they are enabled. Steps to reproduce: - new workpsace - new project, package, CU - open CU in editor - select type name Observe: refactoring actions in context menu are enabled, however in global menu the actions are disabled. - give focus to package explorer - give focus back to editor observe: actions in global menu bar are enabled. Moving to Platform/UI The main menubar's contributions seem to be 1 editor out-of-synch. Also try this: - select text in java editor - edit->copy - switch to another java editor - edit->paste Pastes into the previous editor. Mike: this seems to be the bug you were observing. This seems to occur when switching between two editors of the same type, but not when switching between two different editor types. (If you switch from a java editor to a plugin manifest editor, all the actions point to the right spot... but switch between two manifest editors and everything goes crazy). Agree that this sounds like the same problem. Note that I was seeing it on the Mac, but MichaelV uses Windows. The editor action bars were being updated after the activate event was fired, but the activate listeners for retargetable actions expect the action bars to be up-to-date. This event ordering bug was caused by recent workbenchpage refactoring. Fixed in HEAD. *** Bug 93032 has been marked as a duplicate of this bug. *** Verified in I20050510-0010 |