Good idea.
> On Sep 20, 2018, at 10:46 AM, Alex Harui <[email protected]> wrote:
>
> Feel free to add a warning to the compiler.
>
> On 9/20/18, 12:41 AM, "Harbs" <[email protected]> wrote:
>
> I was just hit by a strange error in IE. It turns out that I was using
> “new Event” without importing org.apache.royale.events.Event. This became a
> browser Event instead of a Royale event and you can’t “new” events in IE…
>
> I’m not sure if there’s something we can do about this, but it’s not a bad
> idea to at least document the potential problem.
>
> Harbs
>
