[ddots-l] Re: Reason Access
- From: D!J!X! <megamansuperior@xxxxxxxxxxx>
- To: <ddots-l@xxxxxxxxxxxxx>
- Date: Wed, 5 Oct 2011 13:38:51 -0400
Well one of the first things we need to determine is how much text or usable
information does each window have. The rear of the rack forexample use to be
all pictures of wires that you'd drag and drop, and they would always move,
so hsc was not useful in that circumstance. Not sure about now, but these
are just certain things that we'd need to look at to see what is doable,
what can and can't be done etc.
When writing scripts the best way (in my opinion) is to do section by
section, or in this case, window by window.
But we must have an understanding on how each windows was designed to work,
and how the designers expect you to use them. That way you develop scripts
that are transparent and don't alter the use of the feature/program. Unless
you have to for whatever reason develop such work arounds (which you might),
when scripting you should keep it as transparent as possible.
Give me some time to take a look at it and pke around behind the window
structure etc, and we'll go from there. That way if and when we contact
propellerhead we'll have some solid stuff to go on, not just questions and
ideas.
HTH, D!J!X!
_____
From: ddots-l-bounce@xxxxxxxxxxxxx [mailto:ddots-l-bounce@xxxxxxxxxxxxx] On
Behalf Of Greg Steel
Sent: Wednesday, October 05, 2011 1:30 PM
To: ddots-l@xxxxxxxxxxxxx
Subject: [ddots-l] Re: Reason Access
Cool thanks. I haven't bought the program yet. Should I contact them and
see if they can give me an explaination of the windows and each device? I
think that each device will need to be done separatly.
----- Original Message -----
From: D!J!X! <mailto:megamansuperior@xxxxxxxxxxx>
To: ddots-l@xxxxxxxxxxxxx
Sent: Wednesday, October 05, 2011 10:24 AM
Subject: [ddots-l] Re: Reason Access
One of the issues will be how to determine all these different items. What
do you rely on to do it. Color? Does the program have a hidden window (like
sonar) where these changes are reported? Is there some kind of access plat
form like UI automation in place? These might be questions you might want to
ask propellhead, it'll make life easier, than having to write custom code in
jaws for it to try and figure out which window is open or not open. You
could always look for uniuque class ID's on screen, or take window handles
and go that way, but that is then assuming that those windows use static
handles or ID's etc.
Another important issue is to give some kind of access to these windows. For
example, when you press down/up arrow, for jaws to report what
track/instrument you are focused on etc.
I'm sure there's more stuff that has to be looked into, but these are my
first impressions from reading your text (which is a good start by the
way!). I've played a little with the program, though I confess I was looking
more at the sounds and what's new then at accessibility.. When I have more
time I'll do some poking around with the script utility tool to see what I
can find...
HTH, D!J!X!
_____
From: ddots-l-bounce@xxxxxxxxxxxxx [mailto:ddots-l-bounce@xxxxxxxxxxxxx] On
Behalf Of Greg Steel
Sent: Wednesday, October 05, 2011 12:47 PM
To: ddots-l@xxxxxxxxxxxxx
Cc: midimag@xxxxxxxxxxx
Subject: [ddots-l] Reason Access
Here is what I want to call the jaws scripts for reason. I started writing
some ideas in notepad. They aren't done yet I don't know how to write
scripts yet but I thought I would share this with everyone. Let me know
what you think.
Other related posts:
