> On Mar 6, 2017, at 6:24 PM, Alex Harui <[email protected]> wrote: > > > > On 3/6/17, 8:05 AM, "Harbs" <[email protected]> wrote: > >> Actually, it looks like it’s only implemented to make the compiler happy. > > Hmm. In my copy of EventDispatcher.as, hasEventListener calls > goog.events.hasListener. The SWF side picks it up from > flash.events.EventDispatcher. > > With this and the problem with int.MAX_VALUE, it makes me wonder if you > are pointing at old code somehow.
You did not understand what I meant. willTrigger is not actually used in TLF. It’s implemented in two classes to complete the implementation of IEventDispatcher. >> >> I’d be interested in trying out dual. How could it work on the swf side >> if willTrigger is not implemented? > > Implementing willTrigger for JS is a separate issue, IMO. On the SWF side > willTrigger is part of flash.events.EventDispatcher. Didn’t follow, but I guess I’ll just wait until dial is ready, and you can explain fully then… ;-) >> And how does it work when the JS side and swf side have different >> signatures (i.e. flash Event vs. Object)? > > In dual, you can use [SWFOverride] metadata to get the compiler to allow > different signatures. More on this when I get dual up and running. > > -Alex >
