Hi Gene,
Gene Amtower wrote:
> So, what you're saying is that I can create a new object during
> "construction" using the getChildControl() method with a special control
> name like "my-widget" and use it in my child handling code (Listeners,
> etc.) without specifying a special appearance ID, allowing the object to
> use the default appearance but allow me to access it later through
> getChildControl() again with the same control name.
Yes, that's right. If you create a custom button (extend
qx.ui.form.Button) and you do *not* override the appearance of the
button your appearance ID of your child control is
"button/my-widget"
if the ID inside the "_createChildControlImpl" is "my-widget".
> The only thing I'll need to do is create the overridden
> _createChildControlImpl() method to direct the object creation as needed
> for each special control name that I use. Is that right?
Absolutely :)
> Wow, that would mean I have been making it more complicated than
> necessary! I think this little detail deserves some mention in the
> documentation somewhere, as I completely missed the special importance
> of getChildControl() combined with the _createChildControlImpl() in my
> reading. The use of _createChildControlImpl() is not mentioned anywhere
> in the online docs based on the results of a search for it.
I'll add this point to my to-do list :)
cheers,
Alex
------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables unlimited
royalty-free distribution of the report engine for externally facing
server and web deployment.
http://p.sf.net/sfu/businessobjects
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
