Chris,
You should use Windows Name rather than Class Name. That distinction was
one of the main features of this new version.
Aaron
On 4/22/2010 9:33 PM, Chris Belle wrote:
Hey guys,
First of all thanks so very much for the hard work on hotspot to
improve it.
This is going to be a great tool when the bugs are worked out.
It just gets better and better, like the mouse positioning is better,
and the improved export, and ability to organize actions better.
I took hotspot for a spin on a clean install and this is what I found.
When working with two different vst windows in sonar, I'm not able to
differentiate my spots, because the window class is the same for both
vst plug-ins, I used sessiondrummer 3 and sfz.
Also, when I tried to create a spot for sessiondrummer3 that used the
same hotkey as the load key for sfz, it wiped out and replace my
hotspot without prompting me.
So along with window class, or app name, we desperately need something
like a top level window name or some unique id to identify each
separate plug-in so spots won't trigger in the parent app or because
they have the same class.
I'm sure that class designation will come in handy elsewhere, but so
far, it's not working in sonar's plugs.
Please take this as constructive criticism, I really appreciate the
time and attention being given to this script, it will help me greatly
when this issue gets solved.
Thank you very much.
At 04:14 PM 4/22/2010, Aaron Smith wrote:
Greetings,
We're very excited to announce the latest version of the widely
popular HotSpot script. This version contains many of the features
requested since the release of the previous version. Here's the
official list of changes.
Version 3.2
4/22/2010 5:12:17 PM
* This version of HotSpot boasts a significant number of changes
from the previous version, hence the significant version number jump.
* The HotSpots dialog has been redesigned. Both HotSpot categories
and HotSpots are presented in list views for easy navigation. The
Import and Export options have been moved to a menu bar inside the
HotSpots dialog. HotSpots also have a menu under the Script Menus
menu in the Window-Eyes control panel.
* HotSpots can now be associated with a specific window, or a
specific class of window, or all applications. This greatly increases
the granularity in regards to exactly where a HotSpot should act.
* HotSpots are no longer dependent on the position of the mouse,
but can instead set the position of the mouse as an action. Mouse
positions can also be set to automatically adjust when the associated
window is resized or repositioned.
* HotSpot actions can now be edited, and organized.
* You now have the option of importing and exporting specific
HotSpots rather than having to import or export your entire HotSpot
collection.
* The documentation has been updated. Please review it to read how
the new features work. You can access the readme from the HotSpots
dialog's Help menu, or the HotSpot menu under the Script Menus menu.
PLEASE NOTE: It is possible, maybe even likely, that previously
defined HotSpots will not function. It is strongly recommended that
you redefine existing HotSpots to take advantage of the newly
provided functionality.
Enjoy!
Aaron
--
Aaron Smith
Product Support Specialist * Web Development
GW Micro, Inc. * 725 Airport North Office Park, Fort Wayne, IN 46825
260-489-3671 * gwmicro.com
To insure that you receive proper support, please include all past
correspondence (where applicable), and any relevant information
pertinent to your situation when submitting a problem report to the GW
Micro Technical Support Team.
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.
--
Aaron Smith
Product Support Specialist * Web Development
GW Micro, Inc. * 725 Airport North Office Park, Fort Wayne, IN 46825
260-489-3671 * gwmicro.com
To insure that you receive proper support, please include all past
correspondence (where applicable), and any relevant information
pertinent to your situation when submitting a problem report to the GW
Micro Technical Support Team.
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.
