Please file a Radar bug against VoiceOver component about double speaking when the VO cursor follows mouse cursor synching is enabled. The reason why you see it in your app more than the other apps is because you currently have the slow performance issue, which allowed you to hear distinctly the second speak cutting off the first speak. By the way, you should run the sample tool to determine where the slowdown is occurring.
Patti Hoa VoiceOver Engineer
On Sep 16, 2009, at 1:35 PM, Xiang Cao wrote:
Another problem I encountered is with mouse moved VO cursor. When I set the VO cursor follows the mouse cursor, strange things happened. The hit test works great. It is enable to find the deepest element under my mouse. But when I move my mouse from one element to another, the voice over start to read the new element very quickly, but the vo cursor has not been moved to the new element. After 0.5 second of computing, the vo cursor finally moved to the new element but the voice over starts to read it again and the first reading is cut. So it sounds like a double hit every time. I’m not sure what I did wrong. Because other app does not behave like this.
Any ideas? Thanks.
Xiang
Do not post admin requests to the list. They will be ignored.
Accessibility-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
|