Re: trying out UI browser and example
Re: trying out UI browser and example
- Subject: Re: trying out UI browser and example
- From: Axel Luttgens <email@hidden>
- Date: Mon, 14 Jun 2010 18:32:34 +0200
Le 14 juin 2010 à 06:43:59, Yuma Antoine Decaux a écrit :
> You wrote:
>
>
> But those considerations left aside, I'm still wondering about the action you described in a previous message: "move with the voice over cursor until reaching the timeline which is 11 key presses away". Could describe each of those eleven key presses? Because I currently am unable to consistently reproduce a way to systematically drop a loop on a track at the right location.
>
>
>
> THere is a missing script element to that. Because the drop zone of the loop is so random, you need to actually cut it , go to the beginning of the track by means of the return key and paste it.
>
> Blind users can't chop their loops in garage band as that is really inaccessible but there are half way workarounds to it. Either one gets to bind an incremenntal nudge to a key or use a midi controller.
Hello Yuma,
I fear I'll have to investigate somewhat further. ;-)
> I would be interested in knowing how you translate a voice over cursor position to a certain element on an UI because i did the following but it just doesn't work
>
> tell application "VoiceOver"
> press
> Move vo cursor to {scroll area 2 of window 1} //since this is relative position it should be fine
> release
> End tell
If you allow, I'll try to share what I've begun to understand, hoping it wouldn't be too misleading.
According to VoiceOver's dictionary, commands "press" and "release", as well as "click", seem to be known by the mouse cursor. So, unless I'm wrong, this should be more correct:
tell application "VoiceOver"
press mouse cursor -- or: tell mouse cursor to press
-- do something
release mouse cursor -- or: tell mouse cursor to release
end tell
On the other hand, "move" indeed is a command intended for the vo cursor. Of course, I guess one would need to configure VoiceOver so that the mouse cursor follows the vo cursor, or to explicitely make use of the VO + Cmd + F5 key combo.
Now, looking at the dictionary again, the "move" command doesn't allow to move the vo cursor to arbitrary locations:
move [up/down/left/right or into item/out of item] : The direction to move in.
[to dock/desktop/menubar/menu extras/spotlight/linked item/first item/last item] : The place to move to
In fact, the move command seems to allow to code a subset of the VO navigation commands; for example, you may want try this one:
tell application "VoiceOver"
tell vo cursor to move to first item
end tell
Outside of those targets enumerated in a limitative way, the move command doesn't even know about UI elements owned by other application processes.
But perhaps might System Events be of some help?
For example:
tell application "System Events"
tell application process "GarageBand"
position of scroll area 2 of window 1
end tell
end tell
This will return a two-integers lists, such as {503, 134}.
Why take the position, instead of a reference to the scroll area, as you have tried in your code snippet? I doubt VoiceOver would be able to do the slightest thing with such a reference; on the other hand, the mouse cursor has a "position" property that looks like to be settable...
But... there's always a but...
This will be for another message, the one I promised the other day.
Axel
_______________________________________________
Do not post admin requests to the list. They will be ignored.
AppleScript-Users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
Archives: http://lists.apple.com/archives/applescript-users
This email sent to email@hidden