This is really annoying.
This happened to me back in January and now it has happened again.
I've followed all the advice in the previous posts to no avail.
Can someone from Adobe please throw me a clue here? Why would -
accessible in the project properties suddenly stop working?
As you may have guessed, it has stopped working for me again. The
cause is a complete mystery.
Guy
On 16/01/2009, at 12:49 PM, Guy Morton wrote:
And as mysteriously as it stopped working, it started working
again.... *shrug*
Guy
On 16/01/2009, at 8:45 AM, Guy Morton wrote:
To answer your other question, I also wondered if it was my client,
so have checked the binary in Safari, Firefox and Opera and all
agree there is no accessibility on offer.
On 16/01/2009, at 4:21 AM, Anthony DeBonis wrote:
Try compiling with accessible turned off and get the swf size - when
you turn accessible compile back on the swf size should be a bit
larger. This will tell you if the compile is backing in the needed
classes. If so it may be the client tool you're using to run the
application. Can you give more information?
--- In flexcoders@yahoogroups.com, Guy Morton <g...@...> wrote:
>
> I had been successfully compiling my app via flexbuilder 3 using
the
-
> accessible compiler flag. Then it stopped working, for no apparent
> reason. I tried reinstalling fb but it made no difference. The
> compiler option is still set but now my app gets compiled with no
> accessibility features.
>
> Anyone got any ideas as to why this might have happened or how to
fix
> it?
>
> Guy
>
