Excellent information! I copied the original code and made a few
modifications and it has worked quite well for the past year. The only risk
I take is if the function I am overriding gets deprecated in the future.
On a side note, when I was working last night I had to comment out a line of
code because it wouldn't compile with it in. And looking at my code I just
can't figure out what the line was doing. It was creating a Tree, adding
TreeFolder and TreeFiles, and the line I removed was T_1.setIndex(indx)
where T_1 was a TreeFile. I looked all the way back to .6.5 and didn't see
it in the docs. I was setting it for every TreeFile I was creating. Did the
old Tree need index values for the TreeFiles? Is that what it was doing?
Commenting out that line still works (to the best of my knowledge). Oh well,
just was wondering...
Thanks,
Jim
On 8/12/07, Derrell Lipman <[EMAIL PROTECTED]> wrote:
>
> On 8/12/07, Jim Hunter <[EMAIL PROTECTED]> wrote:
> >
> > So over-riding the current functionality of an object may not be a good
> > idea, but what do I do when I need to do it? I need to ever-ride the way a
> > table handles _updateStatusBar. I was able to do it with .6.5 by simply
> > creating a new method for it and applying it to the Proto of the table, but
> > I haven't found a way to do it yet in .7.1 so currently I have that
> > functionality disabled. What I am doing is changing the message that is
> > displayed on the bottom of the table. What is the official way to do this?
> >
>
> If you're writing a subclass, you can just have a method of the same name
> in your subclass and it will override the superclass' method of that name.
> If you want to call the superclass' method from your subclass' method, you
> call this.base(arguments).
>
> If you're trying to override the method using a mixin by calling
> qx.Class.include(), it'll complain at you because you're likely to break
> something by doing that. If you really, really, really know what you're
> doing and want to override a method from a mixin, then call qx.Class.patch()
> instead of qx.Class.include().
>
> Derrell
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems? Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> qooxdoo-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
