Hey Ariel.
I am traveling much of the day today, so will throw something together
on the plane.
Cheers; P.
On Apr 8, 4:29 pm, Ariel Flesler <afles...@gmail.com> wrote:
> (Reply to either)
>
> Can you make a demo out of this ?
> Please put the unminified version of jQuery 1.3.2.
>
> --
> Ariel Flesler
>
> On Apr 8, 4:52 pm, Paul Thiel <pjth...@gmail.com> wrote:
>
> > Hi guys.
>
> > Trying again as not sure what happened to the previous post.
>
> > I am using jQuery 1.3.2 and getting some unexpected behavior this
> > morning.
>
> > This works, with the alert being executed when the showpalette event
> > is triggered.
>
> > $().bind('showpalette', function() {
> > alert('showing palette!');
>
> > });
>
> > $.event.trigger('showpalette');
>
> > However, this does NOT work:
>
> > $().bind('show.palette', function() {
> > alert('showing palette!');
>
> > });
>
> > $.event.trigger('show.palette');
>
> > Also, trying to trigger the event with an event object, thus:
>
> > $.event.trigger({
> > type : 'showpalette',
> > palette : palette
>
> > });
>
> > ... also does not work with the bound handler seeing 'undefined' as
> > the second parm (after the event object).
>
> > If I trigger the event like this:
>
> > $.event.trigger('showpalette', [palette]);
>
> > ... it is getting though to the handler just fine.
>
> > What am I missing? Namespacing your events should be just fine in
> > this scenario, right?
>
> > Is there something about $.event.trigger() that is different to $
> > ('#elem').trigger()??
