Understood – I hope this gets addressed/patched in MT 122. Thanks Jan!
It would seem the new AIR release has a lot more bugs than the
previous one... Weird.
On Dec 9, 3:17 pm, Jan Kassens <[EMAIL PROTECTED]> wrote:
> Air 1.5 has a bug with function.caller support.
>
> The current edge in MooTools I removed the usage of function.caller
> for AIR, you may download a full build from here: kassens.net/mootools-
> dev.js
>
> On Dec 9, 2008, at 14:29, Oskar Krawczyk wrote:
>
>
>
>
>
> > Just checked the same code against MT 1.2dev (build 1500) and it works
> > fine.
>
> > MT Core Devs?
>
> > On Dec 9, 12:26 pm, Oskar Krawczyk <[EMAIL PROTECTED]> wrote:
> >> Hi folks,
>
> >> Any AIR devs in the house?
>
> >> I recently resurrected one of my old projects and tried to update it
> >> with MT 1.2.1 (used 1.11 back then) but unfortunately I'm
> >> encountering
> >> some issues.
>
> >> What I'm trying to do is a totally simple el.fade('out') and guess
> >> what, nothing happens and on top of that I'm getting this from the
> >> app:
>
> >> TypeError: Null value
> >> at app:/lib/mootools/mootools-1.2.1-core.js : 1119
> >> at app:/lib/mootools/mootools-1.2.1-core.js : 3359
> >> at app:/lib/mootools/mootools-1.2.1-core.js : 1053
> >> at app:/lib/mootools/mootools-1.2.1-core.js : 3392
> >> at app:/lib/mootools/mootools-1.2.1-core.js : 1580
> >> at app:/lib/mootools/mootools-1.2.1-core.js : 3402
> >> at app:/air-hud.html : 37
> >> at app:/lib/mootools/mootools-1.2.1-core.js : 1965
> >> undefined at undefined : undefined
> >> undefined at undefined : undefined
> >> undefined at undefined : undefined
> >> undefined at undefined : undefined
> >> undefined at undefined : undefined
> >> undefined at undefined : undefined
> >> undefined at undefined : undefined
> >> undefined at undefined : undefined
> >> undefined at undefined : undefined
> >> undefined at undefined : undefined
> >> undefined at undefined : undefined
> >> undefined at undefined : undefined
> >> undefined at undefined : undefined
> >> undefined at undefined : undefined
> >> undefined at undefined : undefined
> >> undefined at undefined : undefined
> >> undefined at undefined : undefined
> >> undefined at undefined : undefined
> >> undefined at undefined : undefined
>
> >> Any idea what's up with that?
>
> --
> Jan - MooTools comitter
> twitter/blog:http://kassens.net
