| Summary: | [ltk] unchecking element in filtered change tree should not uncheck hidden children [refactoring] | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Markus Keller <markus.kell.r> |
| Component: | UI | Assignee: | JDT-UI-Inbox <jdt-ui-inbox> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | 3.2 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | stalebug | ||
Not for 3.2 This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. |
I20051214-2000 - rename Try to Try2 and update similarly named elements and textual matches: public class Try { void m() { Try aTry= new Try(); System.out.println("Try"); } } - on the preview page, check the Textual Matches filter, and then click on the checkbox next to m() => was: All elements become unchecked, also hidden other changes are disabled. => expected: All *visible* children should be unchecked, and the checkbox should become gray (since there are hidden checked children). This would allow to quickly uncheck a whole change group (e.g. visibility adjustments, ...) while leaving all the other changes enabled. The current behavior is confusing since you can inadvertently lose changes from other groups.