Unfortunately, you can't augment actual properties of a custom event
when firing it - everything needs to be passed through memo.
- kangax
On Mar 25, 5:42 am, Jean-Philippe Encausse <[EMAIL PROTECTED]>
wrote:
> Exactly,
> Is there a way to set/override the element or the X,Y mouse location ?
>
> On you code I did:
>
> onInterrupt: function(event) {
> var target = Event.element(event);
> var eX = Event.pointerX(event);
> var eY = Event.pointerY(event);
>
> document.fire('state:active', { idleTime: new Date() -
> this._idleTime, target: target, eX: eX, eY: eY });
> this.setTimer(target, eX, eY);
>
> },
>
> Then I retrieve elements by using:
>
> e.memo.eX // <= The x location
> e.memo.eY // <= The y location
> e.memo.target // <= The element where the mouse is
>
> This is used to display a tooltip when mouse is idle (that's why I
> need mouse location). But it would be cleaner if I override the
> default event parameter ? (I thinks it is not possible because it
> would breaks Event.observer internal mechanism)
>
> On 21 mar, 19:22, kangax <[EMAIL PROTECTED]> wrote:
>
> > Jp,
>
> > I'm not sure I understand what you mean.
> > Custom event that you fire has all of the above mentioned methods:
>
> > $(document.body).fire('foo:bar').element(); // => <body>
>
> > // or a little more clear:
>
> > document.observe('foo:bar', function(e) {
> > e.element(); // <= this will be a <body> element
> > e.pointerX(); // <= this will be NaN, since mouse location is never
> > set
>
> > });
>
> > $(document.body).fire('foo:bar');
>
> > - kangax
>
> > On Mar 21, 6:49 am, Jean-Philippe Encausse <[EMAIL PROTECTED]>
> > wrote:
>
> > > Hi,
>
> > > I would like to fire an event when mouse is idle so I use the code of
> > > kangax:http://thinkweb2.com/projects/prototype/detect-idle-state-with-custom...
>
> > > But I would like the oberver receive an Event with target, x, y mouse
> > > location
> > > So I modify the code to forward the target in the event.memo
>
> > > document.fire('state:idle', { target: target });
>
> > > But I'm looking for a cleaner way to send a well formed event that
> > > works with:
> > > - Event.element(event)
> > > - Event.pointerX(event)
> > > - Event.pointerY(event)
> > > Instead of doing event.memo.target.
>
> > > Any idea ? Solution ?
> > > Best Regards,
> > > Jp
>
> > > On Feb 4, 3:35 pm, Tobie Langel <[EMAIL PROTECTED]> wrote:
>
> > > > I don't have a timeframe for this unfortunately.
>
> > > > And yes, the API will change quite a bit as we'd like to map it more
> > > > closely to ruby's Test::Unit implementation.
>
> > > > I'm not far enough into refactoring to know how backward-compatible
> > > > this rewrite will be.
>
> > > > Will make sure to let you know as soon as I have more info.
>
> > > > Best,
>
> > > > Tobie
>
> > > > On Feb 4, 3:03 pm, "Nic Williams" <[EMAIL PROTECTED]> wrote:
>
> > > > > What's your timeframe for finishing this? Will its API change much?
> > > > > I started doing screencasts of "how to use unittest" today for
> > > > > peepcode.
>
> > > > > If this patch is not useful, then it suggests the current
> > > > >Event.simulateMousecode should be removed as part of the refactoring.
> > > > >Force
> > > > > people to go looking for a tested, known working library to perform
> > > > > the
> > > > > simulations rather than attempt to use known non-working code?
>
> > > > > On 2/4/08, Tobie Langel <[EMAIL PROTECTED]> wrote:
>
> > > > > > The reason I'm not too keen on adding this two unit tests is two-
> > > > > > folds:
>
> > > > > > First I think it belongs in Prototype core, secondly, I'm in the
> > > > > > process of rewriting a good deal of unit_tests so I really don't
> > > > > > think
> > > > > > it's a good time to add features to it. I'd rather strengthen it as
> > > > > > much as possible beforehand.
>
> > > > > > Best,
>
> > > > > > Tobie
>
> > > > > > On Feb 4, 1:19 pm, "Nic Williams" <[EMAIL PROTECTED]> wrote:
> > > > > > > Heh. If I am, then I'll be that person "some time in the future"
> > > > > > > :)
> > > > > > > I'm trying to work on unittest; which just happens to co-share a
> > > > > > > repo +
> > > > > > > mailing list with prototype :)
>
> > > > > > > On 2/4/08, Nick Stakenburg <[EMAIL PROTECTED]> wrote:
>
> > > > > > > > > Yes there might be a better/more complete possibility, and
> > > > > > > > > someone
> > > > > > might
> > > > > > > > do
> > > > > > > > > it in the future
>
> > > > > > > > > I think I'd rather see an incremental fix now; AND wait for
> > > > > > > > > someone
> > > > > > to
> > > > > > > > write
> > > > > > > > > an even better version later.
>
> > > > > > > > > Perhaps once this patch is in, someone else will look at it
>
> > > > > > > > You could be that someone ;)
>
> > > > > > > --
> > > > > > > Dr Nic
> > > > > > > Williamshttp://drnicacademy.com-Ruby/Railstraining/devaround
> > > > > > the worldhttp://drnicwilliams.com-Ruby/Rails/Javascript/Web2.0
> > > > > > > (skype) nicwilliams
> > > > > > > (p) +61 412 002 126 / +61 7 3113 3033
> > > > > > > (mail) PO Box 583 Ashgrove 4060 QLD Aus
>
> > > > > --
> > > > > Dr Nic
> > > > > Williamshttp://drnicacademy.com-Ruby/Railstraining/devaroundthe
> > > > > worldhttp://drnicwilliams.com-Ruby/Rails/Javascript/Web2.0
> > > > > (skype) nicwilliams
> > > > > (p) +61 412 002 126 / +61 7 3113 3033
> > > > > (mail) PO Box 583 Ashgrove 4060 QLD Aus
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Prototype: Core" group.
To post to this group, send email to prototype-core@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/prototype-core?hl=en
-~----------~----~----~----~------~----~------~--~---
