I *have* had this issue. At some point, you get a dialog that just says
"Error!" right? Luckily this was a project backed by CVS, so I didn't
really lose too much.
I think this happens when you point ASDT towards an existing directory
that contains a .project, and other Eclipse files. ASDT seems to play
nicely if there is a directory there with *no* existing Eclipse project
files.
Tim Beynart wrote:
Today I had to reinstall Eclipse + FAMES from scratch. When I try to add
a new AS project (using R-Click > NEW ACTIONSCRIPT 2 PROJECT) and point
it to an exisiting directory for a project, Eclipse putters along for
about a minute, then erases all of the directories and throws an error.
Anyone else have this issue?
_______________________________________________
osflash mailing list
[email protected]
http://osflash.org/mailman/listinfo/osflash_osflash.org
_______________________________________________
osflash mailing list
[email protected]
http://osflash.org/mailman/listinfo/osflash_osflash.org
