I have Xcode on my laptop. How would I do that? Sent from my iPhone
On 13 Nov 2012, at 20:40, Yuma Antoine Decaux <jamy...@gmail.com> wrote: > Hey Scott, > > I think you guys should try to pinpoint the issue ui elements with the > accessibility inspector that's bundled with x-code. At least you can see what > part of the interface has problems, and it even tells you whether the > axaccessibility api has been properly coded. > > > Cheers > > Yuma > > > > <zato1.jpg> > > > > "Light has no value without darkness" > Mob: +642102277190 > Skype: Shainobi1 > twitter: http://www.twitter.com/triple7 > > This message is protected by article 4-210 of a certain book of laws but you > don't have to worry about privacy issues if you are the intended recipient. > However, if any freakish circumstance such as ip sniffing, honey pot open > relay servers or an honest mistake caused a transmission error, please advise > the sender and throw your laptop into a bubble bath to avoid all illicit data > retention. > > On 14/11/2012, at 8:41 AM, Scott Chesworth <scottcheswo...@gmail.com> wrote: > >> Hey Yuma, >> >> The issue we're trying to draw their attention to is that in the edit >> window of Pro Tools, counter values (that speak start time, the range >> you have selected etc) have suddenly started just saying "numeric >> text" instead of speaking dynamic information like "beat 3, 480 ticks >> etc". It's also not possible anymore to tell which edit tool you >> currently have selected with VO, or which edit mode you're in. These >> things all worked a treat in Snow Leopard and Lion, but have kicked >> the bucket in ML for some reason even though Avid haven't changed >> anything at their end. So far, I haven't seen the same behaviour in >> any other app, so can't imagine what's causing the issue. >> >> Nektarios, no, they definitely don't. However, I've lost many many, >> hours of my life and a big chunk of sanity arguing that point. >> Currently I have nothing to show for it (other than a sore head from >> all that repetition and cyber wall banging). Things should be >> different, but they're not. That's not down to a lack of effort on our >> part. >> >> I'll reply to the email anyway, keep calm and carry on as the saying goes. >> >> Scott >> >> On 11/13/12, Yuma Antoine Decaux <jamy...@gmail.com> wrote: >>> Hi, could you tell me what the issue with voice over is? I have access to >>> the apple bug reporting system. If i can emulate something similar within >>> one of the standard apps as well, i may be able to have a direct line with >>> the engineers. >>> >>> Let me know >>> >>> Cheers >>> >>> Yuma >>> >>> >>> >>> >>> >>> >>> "Light has no value without darkness" >>> Mob: +642102277190 >>> Skype: Shainobi1 >>> twitter: http://www.twitter.com/triple7 >>> >>> This message is protected by article 4-210 of a certain book of laws but you >>> don't have to worry about privacy issues if you are the intended recipient. >>> However, if any freakish circumstance such as ip sniffing, honey pot open >>> relay servers or an honest mistake caused a transmission error, please >>> advise the sender and throw your laptop into a bubble bath to avoid all >>> illicit data retention. >>> >>> On 14/11/2012, at 6:36 AM, Slau Halatyn <slauhala...@gmail.com> wrote: >>> >>>> Apple's initial response to me was as follows: >>>> Thank you for your email. Apple relies on each application developer to >>>> properly implement the necessary components into their applications that >>>> allow VoiceOver to work correctly. Unfortunately AVID has not provided an >>>> update for ProTools that would allow their software to work correctly with >>>> VoiceOver in OS X 10.8 Mountain Lion. We recommend that you contact AVID >>>> directly to provide them feedback on the features you are finding do not >>>> work. >>>> >>>> Apple Accessibility >>>> >>>> I responded and copied a couple of people at Apple who initially suggested >>>> contacting the accessibility team. I essentially reiterated the fact that >>>> Avid did, indeed, do the necessary work and that, since the problem does >>>> not exist in Snow Leopard and Lion, it's a problem with VoiceOver and >>>> Mountain Lion. I encourage anyone who gets the same canned response to >>>> come back with further support of the argument. >>>> >>>> Slau >>>> >>> >>> >
