Hmm... not sure that that would solve the issue. I can attach the tips fine on mouseover. Attaching is not the problem. When the attachment takes place I need it to fire whatever event Moo uses to show the tip. Not sure onShow would be it, I think it piggy backs something else.
You see what I mean? Just try attaching a tip to anything with a title on mouseover. You will quickly see what I mean. - Daniel On Jan 5, 9:11 am, Michal <[email protected]> wrote: > Actually I suspect you might need to pass an argument with the event, > so something like: > > this.fireEvent('attach', this); > > or > > this.fireEvent('attach', this.tip); > > might be required. > > Michal. > > On Jan 5, 4:54 pm, Michal <[email protected]> wrote: > > > I suspect you could do something like extend the Tips class, and have > > an extended attach method that fires the event: > > > var ExtendedTips = new Class({ > > Extends: [Tips], > > > attach: function(elements) { > > this.parent(elements); > > this.fireEvent('attach'); > > return this; > > } > > > }); > > > However, I've never used Tips, so maybe someone has a better > > suggestion. > > > Michal. > > > On Jan 5, 3:47 pm, csuwldcat <[email protected]> wrote: > > > > Hey guys, wanted to do just-in-time attachment for Tips. I am doing > > > so for a Google maps markers where the addition of said markers is > > > compounding and dynamic in nature. Right now I .attach() the tip on > > > mouseover of the target marker via event delegation. The problem is > > > that the tip does not appear until the second mouseover obviously... > > > > What would be ridiculously sick would be to have an onAttach(); that I > > > could do a: > > > > onAttach: function(tip){ > > > tip.show(); > > > > } > > > > That would rock most certainly rock the Casba. > > > > PS: if there is a glaringly easy way to do this other than fireEvent > > > (); (which I already tried to work in) please impress upon me your > > > mootastic, sage-like wisdom :) > > > > - Daniel
