 |
History
| Log In
|
|
|
|
[
Permlink
| « Hide
]
Sascha Weinreuter - 07 Feb 06 23:37
another example
I consider this a feature, not a bug. Setting enabled=true for a component explicitly is not the same as keeping enabled to whatever value was set by the component constructor (which can in some cases be determined dynamically).
This is subject to discussion, though - maybe in some cases (boolean properties, component properties with value=null) it makes sense to treat explicit setting of default value as resetting the value. Aha, so would "restore default value" make the property display in non-bold text again? Would this also remove it from the .form file?
I basically agree with you that there is a difference between a default value and an explicitly set value, but it does look quite odd in the UI, especially in the case I pictured in the screenshot, don't you agree? Yes, "restore default value" removes the property from the list of modified properties, so it isn't shown as bold and isn't saved in the form.
Any suggestions to make it less odd are welcome. I see, that stuff is so new and hot that I did not think about this possibility at first
A partial solution for the odd look might be not to highlight the property value, but just its name. And you could add a tooltip that tells the user about the "restore default value" if the currently set value is the same as the default. By the way I think the highlighting should be done with blue text like it's done with the inspections. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Usability Problem
Open
Normal
Component-properties are shown as modified (bold) even when they're set to their default value
