| Summary: | FilteredTree should provide information whether new filter look is used or not | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Jacek Pospychala <jacek.pospychala> |
| Component: | UI | Assignee: | Platform-UI-Inbox <Platform-UI-Inbox> |
| Status: | RESOLVED INVALID | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | daniel_megert |
| Version: | 3.5 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
| Bug Depends on: | |||
| Bug Blocks: | 258881 | ||
|
Description
Jacek Pospychala
Eventually this bug could be fixed by implementing generic setEnabled(boolean) for FilteredTree. With current implementation, disabled and enabled FilteredTree look exactly the same. Preferred impl. would be to gray out Filter input field and tree viewer. Looking at this further, more flexible solution would be changing FilteredTree.useNewLook and FilteredTree.useNativeSearchField(Composite) visibility to protected. Necessary e.g. when overriding createControl, as in bug 258953 The newLook field is set to exactly what you pass in and hence you know the value. If you really need it, simply cache it. If you also need to know whether the native cancel and search field is used you can test this using filterText.getStyle() & SWT.CANCEL) == 0. |