Well, the docs are illustrating how lambda works, but regardless, I'd stand by it. If all you want to do is make an element not be clickable, then the example holds up (as it's comment notes). But if instead you want to attach a method from a class to an element and stop the event, it's esoteric to use it for that purpose...
On Wed, Apr 22, 2009 at 12:51 PM, Sanford Whiteman [Mobile] (via Nabble) < [email protected]<ml-user%[email protected]> > wrote: > > > I'd argue that it's a better pattern to have a handler method that calls > the > > other method. It's more transparent that this is what it's doing than > adding > > a lambda function that returns false. > > Well taken, but the example for $lambda in the docs uses it for > exactly this purpose. :P > > > By adding a 'click' event that returns false, you're going to stop > > the click event even if you later remove your click handler. > > Not if you use removeEvents instead of removeEvent. > > --Sandy > > > > ------------------------------ > View message @ > http://n2.nabble.com/-Moo--Return-false-function-tp2669929p2678372.html > To start a new topic under MooTools Users, email > [email protected]<ml-node%[email protected]> > To unsubscribe from MooTools Users, click here< (link removed) >. > > > ----- The MooTools Tutorial: http://www.mootorial.com www.mootorial.com Clientcide: http://www.clientcide.com www.clientcide.com -- View this message in context: http://n2.nabble.com/-Moo--Return-false-function-tp2669929p2678954.html Sent from the MooTools Users mailing list archive at Nabble.com.
