Yeah, I suppose it is just cloning since all of the properties on the original event have already been fixed so none of that work is needed. I'm currently doing exactly what you've said, with the only difference being that I pass the original event to $.Event and then set the type afterward (to keep the chain).
On Jan 28, 1:06 am, Ariel Flesler <[email protected]> wrote: > I think you're not "fixing" the event when calling fix. You're just > cloning it, aren't you ? > > The code to copy the $.event.props is quite short, I'd say you can > redo that yourself. > Just copy the props from the mousemove (fixed) event to a new $.Event > ('drag'). > > -- > Ariel Fleslerhttp://flesler.blogspot.com > > On Jan 28, 5:38 am, Scott González <[email protected]> wrote: > > > Can we use a different property to track fixed events or make the expando > > public? It would be really useful to be able to detect if an event is fixed > > outside of core, or be able to remove the flag to allow the event to be > > fixed again. > > > The problem I'm running into is I have an event that has already been fixed, > > like mousemove. I want to create a new event, like drag, from the mousemove > > event. I can't use $.event.fix(event) because the first thing is does is > > check if the event has already been fixed and bails out if it has. Instead > > I'm using $.Event(event) and then looping through $.event.props and copying > > the properties over from event.originalEvent to event. > > > I suppose an alternative solution would be to add another parameter to > > $.event.fix which would force the event to be fixed. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jQuery Development" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/jquery-dev?hl=en -~----------~----~----~----~------~----~------~--~---
