[osflash] [mtasc]Class not found error on mac os x - Was Re: (Untitled)

[Stefan Fountain]

Hi ubi, Thanks for your reply, however I'm not using Flashout. I'm not using it because I don't want to add another unknown to my development environment (I'm unfamiliar with Eclipse, SVN, Mtasc, ASDT already so learning those first), plus I don't really see the added bonus if you need to use swfmill to add fonts, components etc. so just using eclipse for my scripting environment. Anyway it's not Flashout giving me trouble it's purely the MTASC window within eclipse that's doing the realtime checking which is giving me the class not found errors. I know I have all the class paths set correctly so it's defenitely a ADST or MTASC thing. I actually think it's a ADST thing but can't really find where. Stefan Fountain  hi, stefan. I'm on mac as well have you supplied absolute paths to flashout? I tried (before succeeding) with relative paths, and it never found the main class. then I thought: "it might be working in the mtasc directory, that's why it doesn't find the main" try providing full paths. so, if your project is structured like this /eclipseWSpace/firstTest/ /eclipseWSpace/firstTest/src/mainEntry.as /eclipseWSpace/firstTest/fOutSample.flashout you'll supply the last two lines I typed to the flashout panel if everything is set properly on your syste, then it should definitely work ciao.ubi On Jul 15, 2005, at 12:00 PM, Stefan Fountain wrote: I know a lot of the' class not found errors' on mtasc/osx/eclipse we're fixed. However I'm still getting - type error class not found errors on Mac OS X 10.4.1. I've done the tricks described on this list, using a sym link to bypass the spaces in the path, updated ASDT to 0.7.1 and using the newest MTASC and using eclipse 3.1 and Java 1.4.2 and also tried with Java 1.5.0. However still getting the type error class not found. It is finding the core MM classes but not the local classes. However double checking about a million times if the class paths are correct and they are, and adding the class path to the eclipse project file properties. Kind of lost for options to check, any other options left to look at? should this be posted as a bug or this this a config issue on my machine? Thanks, Stefan Fountain

_______________________________________________
osflash mailing list
osflash@osflash.org
http://osflash.org/mailman/listinfo/osflash_osflash.org