Ralf Sternberg schrieb:
> Hi Sebastian,
>
> > The problem is that we need to support multiple values for each
> > properties. Then we could add some fallback logic to do something like
> > user-value -> appearance-value -> default-value -> null
>
> Yes, that would solve the problem. Then, manu
Hi Sebastian,
> The problem is that we need to support multiple values for each
> properties. Then we could add some fallback logic to do something like
> user-value -> appearance-value -> default-value -> null
Yes, that would solve the problem. Then, manually set properties would
always supe
Just a small additional note:
Currently property values will be applied in this order:
- main application
- create new instance
- constructor
- apply initial appearance
- set propertyX
- apply state appearance
- set propertyY
- configure instance
-
Ralf Sternberg schrieb:
> Hi,
>
> I'm new to qooxdoo and have a problem regarding the concept of themes
> and appearances:
>
> When properties of a control like colors or borders are being set
> manually (e.g. using "setColor()"), the "state" function of the
> appearance can reset those propert
Hi,
I'm new to qooxdoo and have a problem regarding the concept of themes
and appearances:
When properties of a control like colors or borders are being set
manually (e.g. using "setColor()"), the "state" function of the
appearance can reset those properties whenever a state change occurs.
For
