I also have this problem.
Sometimes the bug seems to be triggered by creating a new AS-Class via ASDT.
ASDT creates an empty .as - file and then the error panel reports the
following error message "Could not find a Class or Interface".
This error message seems to corrupt the whole error reporting facilities in
ASDT:
Even after I manually write a class definition into the new .as - file,
this error message keeps appearing, keeping any other error messages from
being displayed.
The error message seems to get "stuck" in ASDT. Even closing and reopening
the project or eclipse or restarting my system does not remove the error
message...
I'd be really grateful if anybody knows how to fix this :-)
best regards,
Kris
At 12:23 21.04.2006 +0100, you wrote:
>Hi
>
>I am using eclipse with adstc and mtasc to edit .as classes. On a good day
>eclipse checks syntax everytime I save an as file, on bad days it doesn't
>even
>try. I can't really figure out any pattern, but sometimes restarting the pc
>fixes it. Has anyone come across this problem?
>
>I followed a couple of tutorials on osflash to set up eclipse, mtasc
>etc. I use
>the Flash IDE to create my swfs, than mtasc to compile the classes, using
>an ant
>build file in eclipse. I guess that means I'm using 'ames'? Some details
>of my
>setup -
>
>Win XP SP2
>Macromedia Flash 8 pro
>JRE 1.5
>
>all this running on a P3 laptop, not exactly a fast machine. Could that
>be the
>problem - if the compile time for checking sytax is too long will eclipse just
>stop trying?
>
>Any help/suggestions appreciated.
>
>Joe Lister
>
>_______________________________________________
>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
