Well, I've managed to write some batch files which can replace
hotspots.ini for new environments if only I could make hptspot load
them without crashing, it won't accept the windows key r or
control-escape to get to the run box so I can feed the string to it.
Now how about a feature to import and replace hotspots with the new
set, and make that command part of the actions we can manipulate in
hotspot, this way one could load or trigger another hotspot set with
a hot-key or make it part of a chain even and this might get around
the limited window name problem till something better gets done.
Any ideas or feedback from the giant brains?
Right now I can hit the run box and type a command to over-write
hotspots.ini with what-ever spots I want for a plug-in, but this is
my temporary cave man approach to a problem which surely has a more
elegant solution.
Thanks a bunch.
At 09:44 PM 4/17/2010, Chris Belle wrote:
Hey guys,
I've been working with hotspot somemore and I've found some
interesting things.
There's just a slight difference in the window name that breaks
hotspots to work between sonar 6 and sonar 8.5 and that is that
sonar 6 uses sonarpdr and sonar 8 uses sonarpdr.exe
So if I edit the hotspots.ini file and change the name, accordingly,
the spots I made for sonar 8.5 will work in sonar 6.
There's got to be a better way to do this, and I'll leave it up to
the programming skills of the author to perhaps come up with an idea.
This is all in the realm of finding the best way to organize
hotspots and make them play nicely with apps that share plug-ins.
Also, something else interesting.
Now what I've been doing is to create spots for a particular app or
plug-in and then export them in to separate files, or cut them out
of an existing file.
I wanted to see what would happen when importing spots that had the
same hot-key for triggering.
Well, the first spot in the file gets the key, the script itself
will warn you if you try and create a spot in the hotspot dialogue
that conflicts with another spot, but not when importing spots.
But the interesting thing is that both spots will work, even though
they share a hot-key, you can't use the hot key but to trigger the
first spot only, but you can trigger the second spot manually from
the dialogue.
So, I'm wondering, since we really need to be able to dynamically
change hotspot environments for many plug-ins, would it be possible
to erase and over-write to the master hotspots.ini file
as a work around
to have more dynamic hotspots environments?
Since you can feed hotspot keys I wonder if you could hit the run
box and do cmd and then run a batch file to dynamically replace the
master hotspot file say when you went from sfz to sessiondrummer 3
and you use alt-control-b as bank for sfz but you needed that same
key as the program browser for session drummer 3.
I'm going to try some things, this is intriguing.
This is way clunky a way to do things, I'm not a programmer, but I
wonder how far I can get hotspot to do what needs to be done till a
programmer makes it dance better than I can 'grin'?
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.
If you reply to this message it will be delivered to the original
sender only. If your reply would benefit others on the list and your
message is related to GW Micro, then please consider sending your
message to [email protected] so the entire list will receive it.
GW-Info messages are archived at http://www.gwmicro.com/gwinfo. You
can manage your list subscription at http://www.gwmicro.com/listserv.
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.
If you reply to this message it will be delivered to the original sender only.
If your reply would benefit others on the list and your message is related to
GW Micro, then please consider sending your message to [email protected] so
the entire list will receive it.
GW-Info messages are archived at http://www.gwmicro.com/gwinfo. You can manage
your list subscription at http://www.gwmicro.com/listserv.
