Summary: | [ltk] support mandatory Changes | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Tom Hofmann <eclipse> |
Component: | UI | Assignee: | JDT-UI-Inbox <jdt-ui-inbox> |
Status: | ASSIGNED --- | QA Contact: | |
Severity: | enhancement | ||
Priority: | P3 | CC: | markus.kell.r |
Version: | 3.5 | ||
Target Milestone: | --- | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Bug Depends on: | 259092 | ||
Bug Blocks: |
Description
Tom Hofmann
2009-06-12 07:56:03 EDT
Bug 259092 and bug 203943 request API to disable (i.e. "lock") individual check boxes. We should first see whether we can go that way. If we can't, we can add a global option to remove the checkboxes from the tree. > It would of course be possible to prevent the user from continuing the > refactoring once the mandatory changes are disabled. Rather than disabling the refactoring, you could also just enable the mandatory changes silently. I think you could already write a subclass of CompositeChange, mark it as synthetic in the constructor, and extend isValid(..) to enable all necessary changes again. |