Summary: | [PropertiesView] property sheet label provider has limited ability (1G5JKHG) | ||
---|---|---|---|
Product: | [Eclipse Project] Platform | Reporter: | Greg Adams <greg_adams> |
Component: | UI | Assignee: | Platform-UI-Inbox <Platform-UI-Inbox> |
Status: | RESOLVED INVALID | QA Contact: | |
Severity: | normal | ||
Priority: | P4 | CC: | hudsonr, mlists, thatnitind |
Version: | 2.0 | Keywords: | needinfo |
Target Milestone: | --- | ||
Hardware: | All | ||
OS: | Windows 98 | ||
Whiteboard: |
Description
Greg Adams
2001-10-11 14:19:23 EDT
There should be a guideline for the PropertySheet. In the past, gray text on the **Value** indicated that multiple objects were selected, all for which that property existed, but that their values were different. You could still edit the value. To indicate that you cannot edit the property, I would suggest gray text for the property label, not the value. What if I had a read-only property "background color", for which the current value was black. I wrote a custom renderer that paints a black rectangle. The value column needs to be reserved for rendering the value, not indicating CellEditor enabled state. Since all this PR was asking for was a way to set "the color or the font" on a per row basis, and since we have provided the ability to set both the foreground and background color or R2.0, I am marking this PR as fixed. Has Color getLabelForeground(Object) been added to LabelProvider? What about getLabelForeground(Object[]) since the property sheet is really displaying the value of multiple objects. I recommend that a gray *background* be used to represent read-only properties, since this best matches a disabled Text control. GA was suggesting a gray foreground. Gray foreground should be used to indicate multiple selection where the values are not all the same. The API must be changed so that the fact that the values are different can be detected. Please move to UI component. Agree that this needs to be surfaced above the SWT level. Moving to UI. Cleaning up defect lists by setting ones without recent traffic to 'REMIND'. As of now 'LATER' and 'REMIND' resolutions are no longer supported. Please reopen this bug if it is still valid for you. |