actually, the biggest reason (the only reason, really) to use the binds
mutator is so you can have a pointer to bound methods for addEvent so you
can remove the event later. MooTools 2.0 will probably introduce a 3rd
argument to addEvent and removeEvent for the binder (the "this") and
basically remove the need for the mutator.
element.addEvent('click', fn, this);
element.removeEvent('click', fn, this);On Sun, Aug 16, 2009 at 2:10 AM, Rolf <[email protected]> wrote: > > Ah! Thanks.. > Too bad it's going to be ditched.. back to .bind then again... > > On Aug 15, 10:18 pm, Aaron Newton <[email protected]> wrote: > > Unfortunately, this is a hallmark of the Binds mutator; it cannot be > > extended. Note that we are deprecating this mutator in MooTools 2.0 > because > > of this and other issues with it. Your only option is to re-declare the > > methods that must be bound in the child class. > > > > On Sat, Aug 15, 2009 at 8:14 AM, Rolf -nl <[email protected]> > wrote: > > > > > It's probaby straight forward and easy, but I guess it's too hot. > > > > > I have a class that uses Aaron's Binds class. > > > I have a second class that extends the first class. I also want to use > > > Binds in that one, so, I have to define a new Binds,or actually merge > > > two together. $merge is not cutting it... > > > > > Thx, > > > Rolf >
