So I have to complain. Flex Builder 3 has been giving me an intermittent headache for the past 8 months or so that I have been working with it. I would say about once a month, the compiler stops compiling the text files I had been working on. That is, it spits out an old version of the project I have been working on without incorporating any of my recent changes into the program. Very frustrating, since it takes a while to figure out what it is going on--so I am editing and reediting code thinking that I am miscoding. So now, if I suspect that my changes aren't being incorporated into the compile, I simply place a trace somewhere into the program, like so:

trace("change 1");

and then increment that change number every time I compile until I am sure that the bug has disappeared for the time being.

I tried searching this issue out on the Flex Bugs site and was able to find several others who had experienced a similar problem, but in all cases the bug issue was closed because the development team was not able to reproduce it. This doesn't surprise me since, as I said above, it only happens to me once a month and I can't seem to find any antecedents to these incidences. Still, once it kicks in it stays for 1-2 days.

Have you experienced a similar issue?

My computer stats: Powerbook G4 17" 1.3 GHz (yes, it is almost 6 years old--but works great!).

[UPDATE: Aug. 12, 2009: Stull intermittently unreliable. Still using the trace function like crazy (sigh)]