Hi Tom. Usually, this problem is called when you do mass imports - what happens is that you can end up trying to import the same class twice, or two classes with the same name. I'd suggest removing all your
import whatever.* statements and replace them with individual class imports. This has worked for me in the past. HTH, Alias On 9/13/05, Tom Lee <[EMAIL PROTECTED]> wrote: > Hi guys, > > > > I just compiled one of my major projects with Flash 8 for the first time. > Wouldn't you know it: I now get a brand new error I've never seen before: > > > > "The class <package1.classname> cannot be imported because its leaf name is > already being resolved to imported class <package2.classname> " > > > > Oddly, I can't find this exact error in the help docs. However, it seems to > correspond roughly to Error 1190: > > > > "The class <A.B> cannot be imported because its leaf name is already > resolved to a previously imported class <C.B>" > > > > For example, compiling import jv.util generates Error 1190 if the statement > import mx.util also appears in the AS file. > > > > So, my question: what's wrong with importing package1.classname in the same > frame as package2.classname? Why is this now taboo? > > > > > > Thanks, > > > > -tom > > > > _______________________________________________ > Flashcoders mailing list > Flashcoders@chattyfig.figleaf.com > http://chattyfig.figleaf.com/mailman/listinfo/flashcoders > > > _______________________________________________ Flashcoders mailing list Flashcoders@chattyfig.figleaf.com http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
