I guess I didn't quite understand what you were trying to get across with respect to Enabled/Disable. I understood it as a Label will work properly if you disable it but the Atom will not. I just did a test to see how the Atom would behave if I manually set a color then disabled the widget and it worked as I would expect, it turned the Atom gray instead of blue. Did I miss interpret what you were trying to teach me? What is the benefit of using a Label as opposed to using an Atom? Or is there a benefit? Why would you choose one widget instead of the other?
Thanks,
Jim
On 9/5/06, Sebastian Werner <[EMAIL PROTECTED]> wrote:
Jim Hunter schrieb:
> Wouldn't modifying the appearance change the color of all labels? What
> if you wanted 3 different labels to be 3 different colors? The setColor
> method should work the same on all widgets.
It's not that we didn't think the same, but it's just not implemented to
make it possible this way currently. We will try to fix this in future
releases.
>
> Instead of using a qx.ui.basic.Label , I use an qx.ui.basic.Atom in it's
> place and get the results I expect with the color property. It just
> seems to work better then a Label.
The appearance handle the enable/disable state. Maybe you wanna take a
look yourself. It removes the color if enabled. If the user sets it
previously it will be removed by the state appearance. If you however
set the color on a atom it will be inherited to the label object. It's
just a feature of style sheets.
Cheers,
Sebastian
>
> Jim
------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
