| Summary: | Provide refactorings that operate when selecting multiple fields/classes/methods/etc. | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Glenview Jeff <junk> |
| Component: | UI | Assignee: | JDT-UI-Inbox <jdt-ui-inbox> |
| Status: | CLOSED DUPLICATE | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | deepakazad |
| Version: | 3.8 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
|
Description
Glenview Jeff
I omitted that this should also apply to including classes and interfaces in the selection. I'm not sure if this should be split into multiple tickets, but there should also be support for applying other refactorings like this to multiple selections. Eclipse should figure out what's in common in the multiple selection and offer whatever refactorings make sense to apply in batch. For instance, if I select several methods, I should get a change method signature refactoring in the context menu. When I select it, I should be allowed to change the return type, add a field, etc. but not be allowed to change the method name because it doesn't make sense. Many mp3 tagging programs operate like this. Also see bug 28810 comment 1. *** This bug has been marked as a duplicate of bug 24161 *** |