On Wed, Mar 28, 2012 at 07:35, Dietrich Streifert <
[email protected]> wrote:
> answering myself:
>
> I came up with the following solution which uses qx.Class.patch:
>
> qx.Mixin.define("my.ui.tooltip.PManager",
> {
> /*
>
>
> *****************************************************************************
> MEMBERS
>
>
> *****************************************************************************
> */
>
> members :
> {
> _applyCurrent : function(value, old)
> {
> this.base(arguments,value,old);
> if(value) {
> value.setRich(true);
> }
> }
> }
> });
> qx.Class.patch(qx.ui.tooltip.Manager, my.ui.tooltip.PManager);
>
> qx.Class.patchwraps the the old overwritten/patched member so it is
> accessible to the this.base call:
>
Actually (unless something has changed recently, and I don't believe it
has), although you may be getting the effect you want, your statement above
does not reflect reality. When you patch a class with a method of the same
name, you eliminate the old method of that name, and replace it with the
patched-in method of that name. A call to this.base() within the patched-in
method is calling the method of that name in the superclass of the class
being patched, not the former version of the method in the class being
patched.
Derrell
------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here
http://p.sf.net/sfu/sfd2d-msazure
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
