| Summary: | Incorrect undo menu contents after changing workbench part | ||
|---|---|---|---|
| Product: | [Modeling] GMF-Runtime | Reporter: | Linda Damus <ldamus> |
| Component: | General | Assignee: | Alex Boyko <aboyko> |
| Status: | RESOLVED WORKSFORME | QA Contact: | |
| Severity: | normal | ||
| Priority: | P1 | CC: | ahunter.eclipse, dmisic, me, shatalin |
| Version: | 2.0 | ||
| Target Milestone: | 2.0 | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
Linda Damus
The fix for bug 184604 addresses the issue of 'activeContext' member initialized to false when the handler is created. With the fix 'activeContext' will be initialized to true if there are operations in the local history. This eliminates the regression for us. Yet, we still have to look at the issue of creating handlers every time workbench part changes as Susan (the person who was fixing 184604 and 162964) suggests. Anthony, is it OK to downgrade the priority and change the target milestone to '-'? Since, there is no regression the issue looks more as an enhancement. We can leave the priority and target as is. Creating handlers every time the workbench part changes should be tracked through a new Bugzilla. The priority and target milestone remain the same. The issue left open until verified. Bug 184746 is raised to address the issue of creating undo/redo action handlers each time workbench part changes. *** Bug 183151 has been marked as a duplicate of this bug. *** It has been fixed in Eclipse UI component [target cleanup] 2.0 M7 was the original target milestone for this bug [GMF Restructure] Bug 319140 : product GMF and component Runtime was the original product and component for this bug |