I event thought of a 3rd way, that calls the 'elementEnter' method from within an extended attach method: http://yetagain.net/sandbox/tipstestnoeventextended/ .
This way, at least the call to an undocumented function remains within the extended Tips class (so if that function ever changes in the future, it should be easily found). Michal. On Jan 5, 8:21 pm, Michal <[email protected]> wrote: > Oops that second link ishttp://yetagain.net/sandbox/tipstestnoevent/ > > On Jan 5, 8:20 pm, Michal <[email protected]> wrote: > > > I created a test athttp://yetagain.net/sandbox/tipstest/, with a > > modified version of my extended class that fires the 'attach' event. > > It does use the undocumented 'elementEnter' method however. The is > > called in a listener to the custom 'attach' event. > > > Also, reading what Nutron wrote, that perhaps a custom event is not > > necessary, I made another (simpler) test > > athttp://localhost:8888/yetagain/sandbox/tipstestnoevent/thatdoes not > > extend the Tips class with a custom event (although it still uses the > > undocumented 'elementEnter' method to show the tip). > > > Not completely sure if this is what you're after though... > > > Michal. > > > On Jan 5, 7:57 pm, nutron <[email protected]> wrote: > > > > To clarify, you're saying that you are creating an instance of tips only > > > when the user actually mouses over something, yes? > > > The reason there's no event fired on attach is because this functionality > > > occurs either on initialize (if you specify elements) or when you attach > > > elements yourself. Therefor the event is something you essentially already > > > have access to - you know it's going to fire when you call "new Tips" or > > > when you call "myTips.attach(elements)". > > > > Events are used when things occur arbitrarily - the user clicks, the ajax > > > returns, the effect ends. There's no reason to add an event here. > > > > On Mon, Jan 5, 2009 at 11:21 AM, csuwldcat-2 (via Nabble) < > > > [email protected]<ml-user%[email protected]> > > > > > wrote: > > > > > 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 > > > > <michalchare...@...<http://n2.nabble.com/user/SendEmail.jtp?type=node&node=2114397&i=0>> > > > > 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 > > > > > <michalchare...@...<http://n2.nabble.com/user/SendEmail.jtp?type=node&node=2114397&i=1>> > > > > 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 > > > > > > <daniel...@...<http://n2.nabble.com/user/SendEmail.jtp?type=node&node=2114397&i=2>> > > > > 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 > > > > > ------------------------------ > > > > View message @ > > > >http://n2.nabble.com/Msg-for-Moo-Devs-on-Tooltips...Maybe-we-need-an-... > > > > To start a new topic under MooTools Users, email > > > > [email protected]<ml-node%[email protected]> > > > > To unsubscribe from MooTools Users, click here< (link removed) >. > > > > ----- > > > The MooTools Tutorial: http://www.mootorial.comwww.mootorial.com > > > Clientcide: http://www.clientcide.comwww.clientcide.com > > > -- > > > View this message in > > > context:http://n2.nabble.com/Msg-for-Moo-Devs-on-Tooltips...Maybe-we-need-an-... > > > Sent from the MooTools Users mailing list archive at Nabble.com.
