Hi Rene,
nothing weird, just something missing.
First of, your widget should be identifiable for the appearance system. You do
this by refining the init value of the appearance property:
properties: {
"appearance": {
refine: true,
init: "testwidget"
}
}
(In some edge cases – including yours – this is all you need. However, you
would rely on an undocumented and experimental feature – so please proceed. See
[1] for more details on this.)
Next, in your theme (Appearance.js) add the following entry:
appearances :
{
"testwidget/datefield": "datefield"
}
With this entry, you're telling the appearance system that in order to get the
appearance of the datefield child control, it should look up the appearance of
the datefield.
Regards
Tristan
[1] http://bugzilla.qooxdoo.org/show_bug.cgi?id=4020
Am 11.03.2011 um 04:14 schrieb rene.olivo:
> Hello Everyone, I have come across what seems to be a bug in the frame, or
> I'm doing something weird. I'm using child controls to make a combination of
> labels and different input types, I know the frame has this implementation,
> but I want to do my own. What happens is that if I try to create the
> DateField as a control, it displays itself in a weird way. I have made an
> example in the playground just so you can see what I'm talking about and what
> I'm doing: Example The same thing happens when I try passing a SelectBox or
> ComboBox, but TextFields and TextAreas display well. Thank you very much for
> your help everyone!
> View this message in context: getChildControl renders buggy DateFields
> Sent from the qooxdoo mailing list archive at Nabble.com.
> <ATT00001..txt><ATT00002..txt>
------------------------------------------------------------------------------
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
