Hi Greg,
Greg Beaver wrote: > > All in all, a very frustrating experience. I've been working on this > for 3 days now with absolutely no luck getting it to display a stupid > selectbox or list properly :). > I can imagine that this is frustrating. What kind of documentation could we add to get that time down? Greg Beaver wrote: > > This sentence: " For every child control a selector is generated which > starts with the first widget which is not a child control itself" > doesn't make any sense. Is the first widget the custom widget? Is it > the top-level child control? > I'm quite sure that it is your custom widget in your case. It depends on the structure of your composed widget but usually the custom widget uses child controls which makes the custom widget the first non child control widget. Greg Beaver wrote: > > I have a widget that refines its appearance id to "programinfo" and a > child widget that is called "movements" which is a list. I have tried > aliasing "programinfo/movements" and "programinfo/list" to "list" and > this has absolutely no effect. The ONLY thing that worked was > explicitly setting the appearance to "programinfo/movements," so perhaps > this is a bug in qooxdoo? It is not matching the documentation in any > case, the selector "programinfo/movements" was never generated. > You can refine the appearance like this: "programinfo/movements" : "list", "programinfo/movements/pane" : "widget" // don't know if thats really needed Does that work? Regards, Martin -- View this message in context: http://qooxdoo.678.n2.nabble.com/odd-rendering-behavior-of-child-controls-tp5091928p5102135.html Sent from the qooxdoo mailing list archive at Nabble.com. ------------------------------------------------------------------------------ _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
