flash actionscript: *****see my other post "changes to .as files not "compiled"*********

I'm starting this new topic because the other title seems to have scared
people away.
Anyhow, this is it...
I make changes to my class definition file, xxx.as
I save, then test do flash internal tests (CTRL-ENTER) to test my app
Sometimes my ActionScript changes are not made, like Flash is using the old
byte code from a previous version of xxx.as

ANYONE ELSE EXPERIENCE THIS/HAVE ANY SUGGESTIONS ???????

--------------------------------------------------------------------------------
-
--------------------Many thanks in advance-----------------------------

--------------------------------------------------------------------------------
-

Yes, ufitzi, you are not alone. I am having the same problem -- say I have a
file called main.fla which includes (possibly by accessing a class in) sub.as.
Once main.fla has been tested, the file sub.as is never reread in that
session, whether it is edited externally or within Flash. Likewise for
checking a file main.as which includes sub.as.

This means I am spending a great deal of time killing and restarting Flash.
Please, can I add my voice to ufitzi's in begging someone to give us a
solution!? Besides writing perfect and perfectly structured code the first
time around....

(if it helps, I am using Flash MX Professional 2004 under Windows XP)

Thanks for the response, ecayer. Obviously this is not an isolated issue,
although for the record I'm also using Flash 2004 Pro on WinXP...

So, it seems that Flash builds byte code for testing, and then ignores the
original source file. What I don't understand is why the fla's are
"re-compiled" for each test, while the .as files are not. My guess is that
there are seperate include librarys for .as files, and that these libraries are
not considered when retesting.

Not to sound ungrateful, but it appears to be another case of poor design and
planning, in effort to speed up the release of MX2004. When I saw that
ACtionScript 2.0 had its face lift, I was rejoicful to be able to work in a
traditional OOP environment. I still appreciate it, but am becoming frustrated
as more issues reveal themselves.

Oh well, hopefully others will begin to experience this as AS2.0 becomes more
widely used, and maybe in teh future we'll see a patch of somekind. All they
need to do is check for changes in any included .as fuiles and rebuild as
needed.......