It's not different in CS3 or easier to fix if you mess up. When using as classpath like "com.UserInterface" you might as well not use one at all. There's nothing unique about it, which it should be.
com.projectA.userInterface.MyClass com.projectB.userInterface.MyClass that's what you should aim for. regards, Muzak ----- Original Message ----- From: "Michael Trim" <[EMAIL PROTECTED]> To: <flashcoders@chattyfig.figleaf.com> Sent: Friday, June 22, 2007 4:43 PM Subject: RE: [Flashcoders] Clashing Class Names Hi Ian, Yes a quick replace all in the classes for swfb (with careful checking of the results) has solved the problem for now. (Although having to update all the class paths in the library manually was a pain, I hope this is easier in CS3). Thanks for your reply it's interesting to know that that is the actual behavior. Michael _______________________________________________ Flashcoders@chattyfig.figleaf.com To change your subscription options or search the archive: http://chattyfig.figleaf.com/mailman/listinfo/flashcoders Brought to you by Fig Leaf Software Premier Authorized Adobe Consulting and Training http://www.figleaf.com http://training.figleaf.com