Hi Matt I probably should have mentioned I'm building on a Mac.
Yes, there are several ways to tell the compiler to build with accessibility on and I've used all of them. None appear to do it any more. You can imagine how frustrating this is. It surely looks like a bug, but one which even reinstalling FB3 won't fix. Guy Quoting Matt Morgan-May <matt...@adobe.com>: > Hi Guy, > > I'm not sure why you're setting the compiler flag, when you're using > FB. You can enable accessibility at the project level in FB via the > options panel. You can also enable it by setting > <accessible>true</accessible> in flex-config, inside the > <mxml-compiler> block. But on the command line, -accessible (or > -compiler.accessible, which it's aliased to) should work. > > Do you have the MS Inspect32 and AccExplorer32 diagnostic tools? If > not, Google for them. You can use them to check the MSAA values in > the app at runtime. > > Hope this helps, > m > > On 1/15/09 1:54 AM, "Guy Morton" <g...@alchemy.com.au> 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 > > > ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.
