Just offering some constructive criticism here. I think it's worth explaining why Oskar's way is, as he put it, the right way.
Here are my comments on אריה גלזר 's example: http://jsfiddle.net/rpflorence/ME4MH/9/ And on Oskar's: http://jsfiddle.net/rpflorence/ME4MH/10/ If you really like using element methods then you could do it this way: http://jsfiddle.net/rpflorence/ME4MH/11/ However, calling `start` on a morph object has less overhead than calling `morph` on an element (though not enough to worry about I don't think). On Mar 20, 2011, at 7:33 AM, אריה גלזר wrote: > You're both going at it way to complex > > element.get('morph') returns the instance of the morph class attached to the > element, letting you do whatever you want with it, including stopping it. > > On Sun, Mar 20, 2011 at 2:57 PM, Steve Onnis <st...@cfcentral.com.au> wrote: > This will work for you. > http://jsfiddle.net/ME4MH/2/ > > little bit more complete > > -----Original Message----- > From: hamburger [mailto:bilidi...@web.de] > Sent: Sunday, 20 March 2011 11:07 PM > To: MooTools Users > Subject: [Moo] fx.morph.stop() missing? > > hello, > I have a problem to stop a running morph process? > please have a look to the following code. here I would like to stop > the transforming my mouseleave > > http://jsfiddle.net/ME4MH/ > > thx for any hint in advance > > > > > > ======= > Email scanned by PC Tools - No viruses or spyware found. > (Email Guard: 7.0.0.21, Virus/Spyware Database: 6.17140) > http://www.pctools.com/ > ======= > > > > > > ======= > Email scanned by PC Tools - No viruses or spyware found. > (Email Guard: 7.0.0.21, Virus/Spyware Database: 6.17140) > http://www.pctools.com/ > ======= > > > > -- > Arieh Glazer > אריה גלזר > 052-5348-561 > http://www.arieh.co.il > http://www.link-wd.co.il >
