Just a quick thought Carlos... that might be simply because Application or some class dependency that Application has is bindable, which injects org.apache.IEventDispatcher related dependencies.
On Mon, 22 Oct 2018, 07:20 Carlos Rovira, <carlosrov...@apache.org> wrote: > Hi > > I found something similar today, I remember this thread. > > What is happening to me is that I create code in Application project, but > then refactor to its own library. > In Application code nothing makes me add "import > org.apache.royale.events.Event" > But when moved to library, compilation failed with "Error: Call to a > possibly undefined method Event." > So I think the problem is that compiling to an Application differs to > compile to library in some way. > I suppose we always want "org.apache.royale.events.Event" right? > > If this doesn't sound strange I can fill an issue in GitHub > > Thanks > > Carlos > > > > El jue., 20 sept. 2018 a las 9:52, Harbs (<harbs.li...@gmail.com>) > escribió: > > > Good idea. > > > > > On Sep 20, 2018, at 10:46 AM, Alex Harui <aha...@adobe.com.INVALID> > > wrote: > > > > > > Feel free to add a warning to the compiler. > > > > > > On 9/20/18, 12:41 AM, "Harbs" <harbs.li...@gmail.com> 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 > > > > > > > > > -- > Carlos Rovira > http://about.me/carlosrovira >
