I'm developing on a mac. I tired restarting the computer anyway. :-)
How would I set a breakpoint in the accessibility classes?
Guy
On 22/04/2009, at 2:59 PM, Alex Harui wrote:
I guess you could set breakpoints to see if code in the accimpl
classes is getting run. When this happens, can you run some other
Windows EXE that and use its accessibility features? Did you try
restarting the computer?
Alex Harui
Flex SDK Developer
Adobe Systems Inc.
Blog: http://blogs.adobe.com/aharui
From: flexcoders@yahoogroups.com [mailto:flexcod...@yahoogroups.com]
On Behalf Of Guy Morton
Sent: Tuesday, April 21, 2009 5:39 PM
To: flexcoders@yahoogroups.com
Subject: Re: [flexcoders] Re: Accessibility stopped working
I have previously done a full clean and rebuild, and it made no
difference.
The link report from a month ago shows the accessibility classes
were being included at that time.
I just did a clean and build and generated a link report...it has
entries like this:
<script name="/Applications/Adobe Flex Builder 3/sdks/3.1.0/
frameworks/libs/framework.swc(mx/accessibility/AccImpl)"
mod="1214927782165" size="3103" optimizedsize="1768">
<def id="mx.accessibility:AccImpl" />
<pre id="flash.accessibility:AccessibilityImplementation" />
<dep id="mx.core:mx_internal" />
<dep id="flash.accessibility:AccessibilityProperties" />
<dep ! id="mx.accessibility:UIComponentAccImpl" />
<dep id="mx.core:UIComponent" />
<dep id="flash.events:Event" />
<dep id="AS3" />
<dep id="flash.accessibility:Accessibility" />
</script>
But still, no accessibility appears in the actual binary.
If I turn it off in the compiler, the link report doesn't have these
entries, so it's clearly *trying* to include the accessibility
features. They just aren't working.
This is very frustrating.
Guy
On 22/04/2009, at 9:38 AM, Alex Harui wrote:
Not sure. Do a full clean and rebuild. Generate a link-report and
see if the accessibility classes are in the SWF
Alex Harui
Flex SDK Dev! eloper
Adobe Systems Inc.
Blog: http://blogs.adobe.com/aharui
From:! &nb sp;flexcoders@yahoogroups.com [mailto:flexcoders@yahoogroups.com
] On Behalf Of Guy Morton
Sent: Tuesday, April 21, 2009 4:08 PM
To: flexcoders@yahoogroups.com
Subject: Re: [flexcoders] Re: Accessibility stopped working
Importance: High
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, a t 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
>
