RE: [flexcoders] Re: Accessibility stopped working
So is the problem that you can't tab on the Mac? Alex Harui Flex SDK Developer Adobe Systems Inc.<http://www.adobe.com/> Blog: http://blogs.adobe.com/aharui From: flexcoders@yahoogroups.com [mailto:flexcod...@yahoogroups.com] On Behalf Of Guy Morton Sent: Wednesday, April 22, 2009 9:03 PM To: flexcoders@yahoogroups.com Subject: Re: [flexcoders] Re: Accessibility stopped working Well...it's certainly been the case that I could tab through my app before. I know I couldn't get the Mac OS to ever read the text out of my app on Mac (works with JAWS ok, sort of, though) On 23/04/2009, at 1:38 PM, Gordon Smith wrote: If the accessibility classes ever get initialized on Mac, I'd be very surprised. Doesn't Capabilities.hasAccessibility return false in all Mac Players? Gordon Smith Adobe Flex SDK Team From: flexcoders@yahoogroups.com [mailto:flexcod...@yahoogroups.com] On Behalf Of Alex Harui Sent: Tuesday, April 21, 2009 11:15 PM To: flexcoders@yahoogroups.com Subject: RE: [flexcoders] Re: Accessibility stopped working Ok, I'm out of my area of knowledge. I didn't even think we had good accessibility for mac. Did we not ship the sources for mx.accessibility.* I'm off duty for the night. Hopefully you'll figure it out. Alex Harui Flex SDK Developer Adobe Systems Inc.<http://www.adobe.com/> Blog: http://blogs.adobe.com/aharui From: flexcoders@yahoogroups.com [mailto:flexcod...@yahoogroups.com] On Behalf Of Guy Morton Sent: Tuesday, April 21, 2009 10:10 PM To: flexcoders@yahoogroups.com Subject: Re: [flexcoders] Re: Accessibility stopped working 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.<http://www.adobe.com/> Blog: http://blogs.adobe.com/aharui<http://blogs.adobe.c!%0d%0a%20om/aharu%0d%0ai> 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 repor! t...it h as entries like this: <def id="mx.accessibility:AccImpl" /> <pre id="flash.accessibility:AccessibilityImplementation" /> <dep id="mx.core:mx_internal" /> <dep id="flash.accessibility:Accessibi! lityProperties" /> <dep ! id="mx.accessibility:UIComponentAccImpl" /> <dep id="mx.core:UIComponent" /> <dep id="flash.events:Event" /> <dep id="AS3" /> <dep id="flash.accessibility:Accessibility" /> But still, no accessibility appears i! n 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 A! dobe Systems Inc.<http://www.adobe.com/> Blog: http://blogs.adobe.com/aharui From:! &nb sp;flexcoders@yahoogroups.com [mailto:flexcod...@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 Impor! tance: 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 compil
Re: [flexcoders] Re: Accessibility stopped working
Well...it's certainly been the case that I could tab through my app before. I know I couldn't get the Mac OS to ever read the text out of my app on Mac (works with JAWS ok, sort of, though) On 23/04/2009, at 1:38 PM, Gordon Smith wrote: If the accessibility classes ever get initialized on Mac, I'd be very surprised. Doesn't Capabilities.hasAccessibility return false in all Mac Players? Gordon Smith Adobe Flex SDK Team From: flexcoders@yahoogroups.com [mailto:flexcod...@yahoogroups.com] On Behalf Of Alex Harui Sent: Tuesday, April 21, 2009 11:15 PM To: flexcoders@yahoogroups.com Subject: RE: [flexcoders] Re: Accessibility stopped working Ok, I’m out of my area of knowledge. I didn’t even think we had good accessibility for mac. Did we not ship the sources for mx.accessibility.* I’m off duty for the night. Hopefully you’ll figure it out. 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 10:10 PM To: flexcoders@yahoogroups.com Subject: Re: [flexcoders] Re: Accessibility stopped working 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 repor! t...it h as entries like this: <tt>mod="1214927782165" size="3103" optimizedsize="1768"> </tt><pre style="margin: 0em;"> <def id="mx.accessibility:AccImpl" /> <pre id="flash.accessibility:AccessibilityImplementation" /> <dep id="mx.core:mx_internal" /> <dep id="flash.accessibility:Accessibi! lityProperties" /> <dep ! id="mx.accessibility:UIComponentAccImpl" /> <dep id="mx.core:UIComponent" /> <dep id="flash.events:Event" /> <dep id="AS3" /> <dep id="flash.accessibility:Accessibility" /> But still, no accessibility appears i! n 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 A! dobe 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 Impor! tance: 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 y! ou 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.
RE: [flexcoders] Re: Accessibility stopped working
If the accessibility classes ever get initialized on Mac, I'd be very surprised. Doesn't Capabilities.hasAccessibility return false in all Mac Players? Gordon Smith Adobe Flex SDK Team From: flexcoders@yahoogroups.com [mailto:flexcod...@yahoogroups.com] On Behalf Of Alex Harui Sent: Tuesday, April 21, 2009 11:15 PM To: flexcoders@yahoogroups.com Subject: RE: [flexcoders] Re: Accessibility stopped working Ok, I'm out of my area of knowledge. I didn't even think we had good accessibility for mac. Did we not ship the sources for mx.accessibility.* I'm off duty for the night. Hopefully you'll figure it out. Alex Harui Flex SDK Developer Adobe Systems Inc.<http://www.adobe.com/> Blog: http://blogs.adobe.com/aharui From: flexcoders@yahoogroups.com [mailto:flexcod...@yahoogroups.com] On Behalf Of Guy Morton Sent: Tuesday, April 21, 2009 10:10 PM To: flexcoders@yahoogroups.com Subject: Re: [flexcoders] Re: Accessibility stopped working 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.<http://www.adobe.com/> Blog: http://blogs.adobe.com/aharui<http://blogs.adobe.c!%0d%0a%20om/aharu%0d%0ai> 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 repor! t...it h as entries like this: <def id="mx.accessibility:AccImpl" /> <pre id="flash.accessibility:AccessibilityImplementation" /> <dep id="mx.core:mx_internal" /> <dep id="flash.accessibility:Accessibi! lityProperties" /> <dep ! id="mx.accessibility:UIComponentAccImpl" /> <dep id="mx.core:UIComponent" /> <dep id="flash.events:Event" /> <dep id="AS3" /> <dep id="flash.accessibility:Accessibility" /> But still, no accessibility appears i! n 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 A! dobe Systems Inc.<http://www.adobe.com/> Blog: http://blogs.adobe.com/aharui From:! &nb sp;flexcoders@yahoogroups.com [mailto:flexcod...@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 Impor! tance: 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 y! ou 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<mailto:flexcoders%40yahoogroups.com>, Guy Morton wrote: > > I had been successfully compiling my app via flexbuilder 3 using the - > accessible compiler flag. Then it stopped working, for no apparent&n! bsp;! > > rea son. 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 >
RE: [flexcoders] Re: Accessibility stopped working
Yep, the sources are there--Gordon, you can set up a Flex library project for the sdk ($FLEX_HOME/frameworks/projects/framework/src). You then need to associate it with your project. I'm not sure if there's a config-based way to do this--I just always stop at a breakpoint in my code, try to step into framework code, and then FlexBuilder will tell me it doesn't have source and prompt me to add it. You'll want to set a breakpoint in the appropriate mx.accessibility.* class (and if that doesn't work, you'll probably want to confirm that your framework breakpoints are working by breaking on something like UIComponent createChildren() or something). -- Maciek Sakrejda Truviso, Inc. http://www.truviso.com -Original Message- From: Alex Harui Reply-to: flexcoders@yahoogroups.com To: flexcoders@yahoogroups.com Subject: RE: [flexcoders] Re: Accessibility stopped working Date: Tue, 21 Apr 2009 23:14:41 -0700 Ok, I’m out of my area of knowledge. I didn’t even think we had good accessibility for mac. Did we not ship the sources for mx.accessibility.* I’m off duty for the night. Hopefully you’ll figure it out. 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 10:10 PM To: flexcoders@yahoogroups.com Subject: Re: [flexcoders] Re: Accessibility stopped working 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 repor! t...it h as entries like this: <def id="mx.accessibility:AccImpl" /> <pre id="flash.accessibility:AccessibilityImplementation" /> <dep id="mx.core:mx_internal" /> <dep id="flash.accessibility:Accessibi! lityProperties" /> <dep ! id="mx.accessibility:UIComponentAccImpl" /> <dep id="mx.core:UIComponent" /> <dep id="flash.events:Event" /> <dep id="AS3" /> <dep id="flash.accessibility:Accessibility" /> But still, no accessibility appears i! n 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 A! dobe Systems Inc. Blog: http://blogs.adobe.com/aharui From:! &nb sp;flexcoders@yahoogroups.com [mailto:flexcod...@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 Impor! tance: 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 y! ou turn accessible compile back on the swf size should be a bit larger. T
RE: [flexcoders] Re: Accessibility stopped working
Ok, I'm out of my area of knowledge. I didn't even think we had good accessibility for mac. Did we not ship the sources for mx.accessibility.* I'm off duty for the night. Hopefully you'll figure it out. Alex Harui Flex SDK Developer Adobe Systems Inc.<http://www.adobe.com/> Blog: http://blogs.adobe.com/aharui From: flexcoders@yahoogroups.com [mailto:flexcod...@yahoogroups.com] On Behalf Of Guy Morton Sent: Tuesday, April 21, 2009 10:10 PM To: flexcoders@yahoogroups.com Subject: Re: [flexcoders] Re: Accessibility stopped working 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.<http://www.adobe.com/> Blog: http://blogs.adobe.com/aharui<http://blogs.adobe.c!%0d%0a%20om/aharu%0d%0ai> 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 repor! t...it h as entries like this: <def id="mx.accessibility:AccImpl" /> <pre id="flash.accessibility:AccessibilityImplementation" /> <dep id="mx.core:mx_internal" /> <dep id="flash.accessibility:Accessibi! lityProperties" /> <dep ! id="mx.accessibility:UIComponentAccImpl" /> <dep id="mx.core:UIComponent" /> <dep id="flash.events:Event" /> <dep id="AS3" /> <dep id="flash.accessibility:Accessibility" /> But still, no accessibility appears i! n 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 A! dobe Systems Inc.<http://www.adobe.com/> Blog: http://blogs.adobe.com/aharui From:! &nb sp;flexcoders@yahoogroups.com [mailto:flexcod...@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 Impor! tance: 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 y! ou 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<mailto:flexcoders%40yahoogroups.com>, Guy Morton wrote: > > I had been successfully compiling my app via flexbuilder 3 using the - > accessible compiler flag. Then it stopped working, for no apparent&n! bsp;! > > rea son. 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 >
Re: [flexcoders] Re: Accessibility stopped working
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: <tt>mod="1214927782165" size="3103" optimizedsize="1768"> </tt><pre style="margin: 0em;"> <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" /> 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 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 >
RE: [flexcoders] Re: Accessibility stopped working
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.<http://www.adobe.com/> 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: <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" /> 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.<http://www.adobe.com/> Blog: http://blogs.adobe.com/aharui From:! &nb sp;flexcoders@yahoogroups.com [mailto:flexcod...@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<mailto:flexcoders%40yahoogroups.com>, Guy Morton 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 >
Re: [flexcoders] Re: Accessibility stopped working
sorry, to answer your question...version 3.1 On 22/04/2009, at 9:38 AM, Matt Morgan-May wrote: What version of the Flex SDK are you running? Have you tried it against a different install of the SDK? I have to say that yours is the only case I've heard of this happening, so my guess is that it's got something to do with either some kind of corruption, or the project's config files. - m From: Guy Morton Sent: Tuesday, April 21, 2009 4:08 PM To: flexcoders@yahoogroups.com Subject: Re: [flexcoders] Re: Accessibility stopped working 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 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 >
Re: [flexcoders] Re: Accessibility stopped working
Well aren't I the lucky one. :-) The only thing I can think of is that mismatched hidden project files are being stored in CVS and getting updated into different installs of flex builder and that that is causing the problems. That said, I've looked at the project files I'm aware of and can't see anything obvious. Guy On 22/04/2009, at 9:38 AM, Matt Morgan-May wrote: What version of the Flex SDK are you running? Have you tried it against a different install of the SDK? I have to say that yours is the only case I've heard of this happening, so my guess is that it's got something to do with either some kind of corruption, or the project's config files. - m From: Guy Morton Sent: Tuesday, April 21, 2009 4:08 PM To: flexcoders@yahoogroups.com Subject: Re: [flexcoders] Re: Accessibility stopped working 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 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 >
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: <tt>mod="1214927782165" size="3103" optimizedsize="1768"> </tt><pre style="margin: 0em;"> <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" /> 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 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 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 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 >
RE: [flexcoders] Re: Accessibility stopped working
What version of the Flex SDK are you running? Have you tried it against a different install of the SDK? I have to say that yours is the only case I've heard of this happening, so my guess is that it's got something to do with either some kind of corruption, or the project's config files. - m From: Guy Morton Sent: Tuesday, April 21, 2009 4:08 PM To: flexcoders@yahoogroups.com Subject: Re: [flexcoders] Re: Accessibility stopped working 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<mailto:flexcoders%40yahoogroups.com>, Guy Morton 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 >
RE: [flexcoders] Re: Accessibility stopped working
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 Developer Adobe Systems Inc.<http://www.adobe.com/> Blog: http://blogs.adobe.com/aharui From: flexcoders@yahoogroups.com [mailto:flexcod...@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<mailto:flexcoders%40yahoogroups.com>, Guy Morton 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 >
Re: [flexcoders] Re: Accessibility stopped working
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 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 >
Re: [flexcoders] Re: Accessibility stopped working
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 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 >
Re: [flexcoders] Re: Accessibility stopped working
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 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 >
Re: [flexcoders] Re: Accessibility stopped working
Hi Anthony Yes, I had the same idea. I checked the binary size from my build against one built by another user using the same codebase - both had accessibility on and his was about 20k biigger than mine. His is accessible, mine isn't. So, it's my FB that's no longer including the accessibility classes. As mentioned in my other post, even a reinstall of FB has not fixed this, so I'm hoping someone here has some other suggestions for what might be wrong and how to fix it. I've looked at .actionScriptProperties in a text editor and it has the right config in it. Guy Quoting Anthony DeBonis : > 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 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.
[flexcoders] Re: Accessibility stopped working
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 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 >
