I've reverted the arguments for the next release. Maybe today, if not, Monday.
On Fri, Oct 23, 2009 at 2:23 AM, DHunt <[email protected]> wrote: > > Oh! Thank you very much for the example, I now understand what kicked > me off track: > I didn't notice the tips events show and hide in 1.2.4 don't have two > arguments like it says in docs... > > 1. tip - (element) The tip element. > 2. el - (element) The element on which the tip is based on. > > ...but just one, the element on which the tip is based on, so I should > access the tips element by this.tip instead. Now it all makes perfect > sense and it actually seems to be a better way. > > I wouldn't change anything, except maybe the docs that show "function > (tip, el)" for the events :) > > Thanks again! > > D.Hunt > > > On 22 říj, 20:08, Aaron Newton <[email protected]> wrote: > > tips in 1.2.4 now toggle display (block, none) by default. The problem > with > > only changing visibility/opacity is that when the tip is hidden it is > still > > floating over your content, intercepting clicks. Thinking about it, I > think > > I can make it default to this behavior but not force it. > > In the mean time, you need to toggle display yourself if you have a > custom > > show/hide method: > > > > http://mooshell.net/twzxf/ > > > > I'll change this if I can to still work like it used to if you override > the > > method. > > > > -aaron > > > > On Thu, Oct 22, 2009 at 4:05 AM, DHunt <[email protected]> wrote: > > > > > Hello, > > > after switching to the (otherwise great!) Mootools 1.2.4 (and > > > 1.2.4.1), I noticed my tips stopped working properly. > > > > > The code I posted tohttp://mooshell.net/DaxXH/used to fade-in the > > > tips div in 1.2.3, while in 1.2.4 it doesn't, and fades-out the > > > element that has the tip applied to when you move the mouse out. > > > Though it does work when onShow and onHide are default, I prefer the > > > slower fading. > > > > > Any ideas what I'm doing wrong? > > > > > Thanks! >
