really the invoke calls are only necessary because i wanted to modify
the behavior of the events a little bit. i think to exactly emulate
mouseenter and mouseleave you don't need to do any of the ancestor
calculation and you only have to observe stopEvent on the element you
fire the custom event o
On 1 okt, 19:15, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
> here's a version that uses custom
> events:http://neverninetofive.com/mouseenterleave/
>
Calling invoke('observe') and invoke('stopObserving') like that is
overkill. The patch I've posted is much easier on the browser since it
obs
On Oct 1, 2:16 pm, EMoreth <[EMAIL PROTECTED]> wrote:
> This is the third time that this happens with me...
>
> First o thought that was my mistake but now i really cant figure out
> why this is happening:
>
> fncHandler : function(evt)
> {
> evt.stop();
> var target = evt.elemen
This is very very cool, and something I spent several hours trying to
figure out last night. Synchronicity! Can you explain a little more
(for someone who doesn't understand custom events at all) what this
magic is? I can see that it works, precisely the same way as Nick's
for all intents
This is the third time that this happens with me...
First o thought that was my mistake but now i really cant figure out
why this is happening:
fncHandler : function(evt)
{
evt.stop();
var target = evt.element();
target.up('.messageItem').update('Sent Message');
}
targe
here's a version that uses custom events:
http://neverninetofive.com/mouseenterleave/
Nick, hope you don't mind, i borrowed your testing template.
On Sep 21, 12:59 pm, Nick Stakenburg <[EMAIL PROTECTED]> wrote:
> That will probably give you some problems with textarea's and input
> elements. I'
