Hey,
I did a quick check on whats going on. The problem is clear to me now:
Using e.g. the virtual select box as child control changes its appearance key
from the default "virtual-selectbox" to "widget/dummy" in the given sample.
Usually, that will not work but the virtual select box has a defau
Ah, yes. I remember that in some cases, it was not possible to detect the
former appearance. If you can supply a sample, I check for the reason why the
fallback could not work.
Am 29.08.2012 um 07:57 schrieb Tobias Oetiker :
> Hi Martin,
>
> Today Martin Wittemann wrote:
>
>> Hey, Hm, that s
Hi Martin,
Today Martin Wittemann wrote:
> Hey, Hm, that should work out of the box as far as I can
> remember. We do have a fallback implementation if there is not
> appearance for the child control, we check if the original
> appearance applies. I quite some time ago I did something in that
> a
Hey,
Hm, that should work out of the box as far as I can remember. We do have a
fallback implementation if there is not appearance for the child control, we
check if the original appearance applies. I quite some time ago I did something
in that area so I might be wrong. Is that true for every ch
Hi,
I found the post [1] quite useful in dealing with the appearance of
child controls.
[1]
http://qooxdoo.678.n2.nabble.com/odd-rendering-behavior-of-child-controls-td5091928.html
See if this is what you are looking for.
Cheers,
Ramakrishna
On 08/28/2012 06:46 PM, Tobias Oetiker wrote
Hi,
I quite like the widget with childcontrols approach for creating my
uis ... BUT eventhough I have not created any special theming
properties, the included child widgets tend to loose part of their
design in the process ...
how can I use controls as child widgets and have them continue to
use
