[realmusicians] Re: hotspot clicker and sonitus eq
- From: "Phil Muir" <info@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
- To: <realmusicians@xxxxxxxxxxxxx>
- Date: Sun, 30 May 2010 22:35:29 +0100
Think it just uses controls in reference to class types. BTW, you can
programme up HSC so that it will search for stuff like that. Never had the
need to do that yet though.
Regards, Phil Muir
Accessibility Training
Telephone: US (615) 713-2021
UK +44-1747-821-794
Mobile: UK +44-7968-136-246
E-mail:
info@xxxxxxxxxxxxxxxxxxxxxxxxxxx <mailto:info@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
URL:
http://www.accessibilitytraining.co.uk/
-----Original Message-----
From: realmusicians-bounce@xxxxxxxxxxxxx
[mailto:realmusicians-bounce@xxxxxxxxxxxxx] On Behalf Of Chris Belle
Sent: Sunday, May 30, 2010 8:28 PM
To: realmusicians@xxxxxxxxxxxxx
Subject: [realmusicians] Re: hotspot clicker and sonitus eq
Yeh, I just realized that.
I just figured out how to search for a color with autohot too.
I love both these tools for different reasons, hsc and auto-hot, and
win-eyes hot spot is just about out of the oven, I've been working solidly
with Aaron to help get it done.
Autohot has the advantage of being a pseudo programming language interface
which can really do some powerful stuff at the system level, outside a
screen-reader, but the down side is that it won't talk directly to the
screen-reader so I have to use message boxes and stuff when variables
trigger.
Window-eyes already had setfiles, very powerful with in themselves, with
hyperactive windows and such which can trigger on colors and speak strings,
etc, and integrated with hotspot, really enhances things.
I've been experimenting a bit with the new hsc, and with it's new
capabilities, when we get the bugs worked out it'll be a real winner.
So these are all excellent tools in their own ways.
What I'm doing with auto-hot is using a variable to determine whether the
color matches or not for band on or off, and then displaying a message box,
clunky, but it works.
Thanks for the tip.
What I really love about autohot is the ability to use hotstrings, which by
their nature can be way more numerous and versatile than hotkeys, and the
ability to get directly hold of window controls.
I saw references to push buttons and such in the hsc files, can hsc operate
directly on controls, or does it just use them for reference with class
types?
Unless the controls change, like they are apt to do with silly soundforge eq
sliders, in most cases, if you operate directly on window controls, you can
thumb your nose at display settings, so your positional stuff won't matter,
because the control is called by name.
Window-eyes setfiles are even more vulernable to window changes than hsc is,
but Aaron is implementing some stuff in to hotspot which will make that less
a problem.
At 01:57 PM 5/30/2010, you wrote:
>I used to get an error message when a band was disabled. To work
>around that, I set-up a recovery HotSpot to the band control in
>question that would say, "Band 1 Disabled." This HotSpot would trigger
>instead of the "hotspot failled" error message.
>
>That's what the RecoverySpot feature is for.
>
>Regards, Phil Muir
>Accessibility Training
>Telephone: US (615) 713-2021
>UK +44-1747-821-794
>Mobile: UK +44-7968-136-246
>E-mail:
>info@xxxxxxxxxxxxxxxxxxxxxxxxxxx
><mailto:info@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
>URL:
>http://www.accessibilitytraining.co.uk/
>
>-----Original Message-----
>From: realmusicians-bounce@xxxxxxxxxxxxx
>[mailto:realmusicians-bounce@xxxxxxxxxxxxx] On Behalf Of Chris Belle
>Sent: Sunday, May 30, 2010 6:34 PM
>To: realmusicians@xxxxxxxxxxxxx
>Subject: [realmusicians] Re: hotspot clicker and sonitus eq
>
>Yes, it can, but I haven't gotten that far yet, I've done just about
>everything but color detection.
>
>But I noticed in your spot definitions for band disable you don't have
>any colors defined.
>
>So how are you telling when the band is disabled?
>
>We click on the band number to enable/disable it and that works fine,
>and the actual slider will change color if the band is enabled if you
>click on it.
>
>But I didn't see that as part of the definition.
>for band disable.
>
>So what criteria are you using,
>and I'll work out the details, thanks.
>
>
>At 07:16 AM 5/30/2010, you wrote:
> >No. Thought AutoHotkey could handle colour detection?
> >
> >
> >
> >Regards, Phil Muir
> >Accessibility Training
> >Telephone: US (615) 713-2021
> >UK +44-1747-821-794
> >Mobile: UK +44-7968-136-246
> >E-mail:
> >info@xxxxxxxxxxxxxxxxxxxxxxxxxxx
> ><mailto:info@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
> >URL:
> >http://www.accessibilitytraining.co.uk/
> >
> >-----Original Message-----
> >From: realmusicians-bounce@xxxxxxxxxxxxx
> >[mailto:realmusicians-bounce@xxxxxxxxxxxxx] On Behalf Of Chris Belle
> >Sent: Saturday, May 29, 2010 4:41 PM
> >To: realmusicians-freelists.org
> >Subject: [realmusicians] hotspot clicker and sonitus eq
> >
> >Well, I think the king of hotspot clicker is hanging around here
> >still, I got a question.
> >
> >I'm working on the sonitus suite for access for the rest of us who
> >like to work outside of jaws sometimes.
> >
> >I've got a pretty nice implementation for the sonitus eq with
> >autohotkey and the band toggles are working fine, but what criteria
> >are you using to tell if the band is enabled or disabled?
> >
> >I know the sliders will change color when you click on them if the
> >band is on, but is there a better way to tell?
> >
> >
> >
> >
> >
> >
> > WARNING!!!
> >
> >This email could contain innocent phrases which, if taken out of
> >context, or read from an existing inclination to be hostile, or an
> >overly politically correct world view could induce cursing, abusive
> >language, or other indications of less than desirable behavior in a
> >public venue.
> >No ill will is intended.
> >The sender takes no responsibility for mis-interpretation or
> >otherwise extrapolated extended meaning, intent, or purposes implied
> >or imagined from said phrases.
> >The receiver of any such email containing such phrases is solely
> >responsible for good interpretation and intelligent deployment of
> >subsequent responses to the above communication.
>
>
>
>
> WARNING!!!
>
>This email could contain innocent phrases which, if taken out of
>context, or read from an existing inclination to be hostile, or an
>overly politically correct world view could induce cursing, abusive
>language, or other indications of less than desirable behavior in a public
venue.
>No ill will is intended.
>The sender takes no responsibility for mis-interpretation or otherwise
>extrapolated extended meaning, intent, or purposes implied or imagined
>from said phrases.
>The receiver of any such email containing such phrases is solely
>responsible for good interpretation and intelligent deployment of
>subsequent responses to the above communication.
WARNING!!!
This email could contain innocent phrases which, if taken out of context, or
read from an existing inclination to be hostile, or an overly politically
correct world view could induce cursing, abusive language, or other
indications of less than desirable behavior in a public venue.
No ill will is intended.
The sender takes no responsibility for mis-interpretation or otherwise
extrapolated extended meaning, intent, or purposes implied or imagined from
said phrases.
The receiver of any such email containing such phrases is solely responsible
for good interpretation and intelligent deployment of subsequent responses
to the above communication.
Other related posts:
