Chris, are you referring to nicknames? Tried using those here today too and
they didn't work. For example:
[nicknames]
Sonitus:fx Compressor=Sonitus_fx Compressor.hsc
I was able to work around that by hard coding the Sonar.hsc file as
described previously Far from ideal though. Suffice to say, Jim's on to
it. Have already been discussing this issue at length with him. Jim's
really good at responding promptly so, I don't think it will take him long
to sort this one out.
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: Thursday, June 03, 2010 2:05 PM
To: realmusicians@xxxxxxxxxxxxx
Subject: [realmusicians] Re: HotSpotClicker Set Name Window Title Switching
Bug
Good call Phil.
I think the problem might go a little deeper than the top window name
matching up even, because I have that problem with the new hot spot clicker
with my sd3 asets switching automatically even.
I have mine hard-wired to specific names in other words, you don't accept
the default name but give it the names specified and that worked flawlessly
with hsc 194.
So I need to do the experiment again and see what names actually get saved.
With autohot and hotspot for window-eyes we can trigger on part of the title
name, or contains , begins with or ends with, or match case or not as we
wish.
I'll let you know what i find on my end and see if we can squash all these
bugs.
At 04:05 PM 6/2/2010, you wrote:
> Hi all!
>
>Have found a bug in the latest HotSpotClicker_196 that prevents automatic
>Window Title switching working as advertised. Let me explain further.
>Note: this bug for some reason does not appear on every system. For
>example, Tim burgess is running Windows XP and he can't repro. I am
>running Windows XP on this laptop currently and I can repro. The bug only
>happens if the following conditions are true. Your HSC set name is
>different to the Window Title. For example, I can see this in any of the
>Sonitus affects. The sonitus Compressor set name is:
>
>Sonitus_fx Compressor.hsc
>
>But the Window title is:
>
>Sonitus:fx Compressor
>
>If the above conditions are met then, the Sonitus Compressor set does not
>load, even though it should. To complicate things further, if you
recreate
>the Sonitus Compressor set then, the Window Title and set name are the same
>as written above though obviously you don't want to do that as you will
wipe
>out the Sonitus Compressor set.
>
>Temporary work around. We can't rename the set because the colon character
>can't be used in Window file names so we shall have to edit the Sonar.hsc
>file. In this example we shall use the Sonitus Compressor set name. If
you
>go into your:
>
>Sonar.hsc
>
>Set and locate the code for the Sonitus FX Compressor and change it so that
>it looks like this:
>
>Sonitus:fx Compressor=Sonitus_fx Compressor.hsc
>
>Then every thing will work as it should and the sets will switch. Note:
you
>can do this with all of the sonitus suite affects. BtW, am nearly finished
>reworking all of the HSC sets into multiple spot rings and will post on
that
>soon.
>
>
>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/
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.
