And yet, even staff members have suggested using the InstallPackages
script. Well, if they encourage it, and it works stable, why not just
include it? I do agree, things like this should have been automatically a
part of a standard installation of WE. Honestly, how much easier is it,
when a new user, who might not evne be that familiar with computing
itself, simply can press a hotkey, and there he goes, and can handle his
scripts. Or the other scripts mentioned here, which GREATLY will improve
the functionality of WE. OK, I agree, there is a long line of scripts,
that only you need when - and if - you are running certain applications,
and really want a given set of features. Yet, there is a good handful of
scripts, that could be defined as more or less BASIC, when comes to
increasing the functionality of WE. The InstallPackages, or the
HomerShared, is just to mention two, since both of these would give a good
stepstone for further script exploring.
Again, I do see the point about support. Maybe some of the staff is more
rightly to answer this question, but really, how often do they give
support on these scripts, in real life? Ain't it so, that most of the
'support' on scripts, are given through the mailing lists, anyway. And, if
so, where does the point about not including those scripts go?
At least, why is there nowhere in WE, a menu choice or something, that
would take you right to SC? If GW do not want to include the
InstallPackage script, at least such a quick-to-get-there choice, would
have been beneficial for many a new user.
----- Original Message -----
From: <mailto:[email protected]>Jeff Bishop
To: <mailto:[email protected]>[email protected]
Sent: Thursday, April 08, 2010 7:44 AM
Subject: RE: hotspot 3.0 is majorlly cool.
Scripts developed by third-party developers will basically then have to be
supported by GW Micro staff. I don't think that is such a good idea
honestly. They have enough on their plate.
From: jim grimsby Jr. [mailto:[email protected]]
Sent: Wednesday, April 07, 2010 10:18 PM
To: <mailto:[email protected]>[email protected]
Subject: Re: hotspot 3.0 is majorlly cool.
because there are quite a few of them that new users are not going to
use. lets take the window-eyes scripting framework script for
example. most users are not going to use that. another example along
this vain is the window tree view script. the im window script. some
people may or may not want we sounds for example. so the scripts they
include should enhance the feature set of window-eyes and still offer
choice to the user. hotspot is one of these types of scripts. I am going
to argue once again for gw micro including some 3rd party scripts. these
will include install packages. this will provide the new user a means of
getting more scripts with out knowing or caring how to deal with sc.
focus controls. activate window. these scripts go a long way at times
to make programs that are not accessible with out them accessible.
elaquence fix. this script will avoid crashes with elaquence.
so it should be installed buy default so once again the user has this
protection in place.
everything else we can get from the install packages witch as I said
should be included with window-eyes.
From: <mailto:[email protected]>Chip Orange
Sent: Wednesday, April 07, 2010 5:14 PM
To: <mailto:[email protected]>[email protected]
Subject: RE: hotspot 3.0 is majorlly cool.
I'm not sure why GW wouldn't include every script they've written with
WE? They're all useful, and why make users go get them? And of course,
including them helps new users who may be unfamiliar with SC.
Chip
----------
From: Rick Alfaro [mailto:[email protected]]
Sent: Wednesday, April 07, 2010 5:28 PM
To: <mailto:[email protected]>[email protected]
Subject: RE: hotspot 3.0 is majorlly cool.
I agree 100%. There is more power here than folks can imagine. This
should definitely be included in the factory scripts.
I'll give an example that I just put together in less than 3 minutes.
If you use Outlook 2007, you will know how annoying it is to read an html
message. For best results one has to tell Outlook to open the message in
your browser. This is normally accomplished by doing the following key
sequence.
Alt-h then x then v.
I just solved my problem by creating a new HotSpot definition that I
assigned to Windows o.
1. Make sure you are in Outlook 2007 with an html message open.
2. Bring up the new hotspot dialog, default key is alt control p.
3. Give it a name, I called it "Open in browser".
4. Assign this definition to a key, I used Windows o.
5. Tab over to add action and press enter.
6. Choose insert key from the list of actions and press enter.
7. You will be in a dialog you are used to seeing when defining a
new hotkey. Press alt c to capture the keystroke and when prompted to
type the key, hit alt h.
8. Repeat the same thing to add x and v as insert key actions.
9. Tab over to add and hit enter.
10. You're done so test it out by hitting Windows o or whatever key you
decided to assign this definition to.
The html message should now open into your browser with just one keystroke.
This works on my system but you may need to tweak this to work on yours by
possibly adding a couple of delays. I didn't need to do that however.
Within the new hotspot dialog you probably noticed some other edit boxes
and buttons that deal with the mouse position. For this example, those
can be ignored because this HotSpot does absolutely nothing with the mouse
pointer.
That in fact, is part of the point of this message. Although HotSpot was
originally created to do things with the mouse, that is no longer the
case. HotSpot 3.0 goes way beyond that now and gives us a whole lot of
power in one easy to use script. Those of us that are not scripters can
really do some cool stuff now beyond what was possible with set files.
Also, if you are an Adaptive Technology Consultant and have run into
situations where set files wouldn't cut it, try using HotSpot 3.0 to
possibly create a solution before trying to get a script written. You
might be pleasantly surprised.
--Regards,
--Rick alfaro
[email protected]
From: Vic Beckley [mailto:[email protected]]
Sent: Wednesday, April 07, 2010 4:13 PM
To: [email protected]
Subject: RE: hotspot 3.0 is majorlly cool.
Aaron,
I second the thought that Hot Spot should be included by default with
Window-Eyes 7.2. It is one of the most impressive scripts to date!
Vic
From: Aaron Smith [mailto:[email protected]]
Sent: Wednesday, April 07, 2010 3:47 PM
Cc: gw-info; [email protected]
Subject: Re: hotspot 3.0 is majorlly cool.
Jim,
Glad to hear you're having success with HotSpot. To address your issues:
1. Key Describer - That was an oversight on my part. I'll get that fixed.
2. Old HotSpots - Correct. They don't port over. I mention that in the
package information dialog during the installation. It seemed to me that
it was more work that necessary since I don't think this script was used
by that many people in past versions.
3. Adding Actions while Adding HotSpots - You should definitely be able to
add actions when adding a HotSpot, as that's how I did all my testing. Can
you give me any more detail?
Thanks for the feedback.
Aaron
On 4/7/2010 3:18 PM, jim grimsby Jr. wrote:
HI, BEEN PLAYING WITH THIS SCRIPT FOR A WHILE NOW AND IT IS MAJORLLY
COOL!!!!! with windows live mail using the find string feature the view
online button is always found to open rss articals. maid moving around
the skype user interface a breaze. just two name two things I have done
with it so far.
ok now I hate to do it but I have to point out a few things here. not
really bad things but things that might need to be addressed. please note
I hate to do it because I love this script so much.
first while in the key describer the hot spot script should not act on hot
spots keys. what it should do is say the name of the hot spot and
indicate that it is a hot spot. for example view online hotspot.
ok old hot spots don't carry out the acctions defined you have to add the
actions back buy using the hot spot manager.
also adding actions while adding a hot spot doesn't seem to work. you can
only add actions from the hot spot manager.
other then that man it is wonderful.
oh one more thing I think this script should be included buy default in
window-eyes 7.2. it is an enhancement that most users are going to want.
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
<mailto:[email protected]>[email protected] so the entire list will
receive it.
GW-Info messages are archived at
<http://www.gwmicro.com/gwinfo>http://www.gwmicro.com/gwinfo. You can
manage your list subscription at
<http://www.gwmicro.com/listserv>http://www.gwmicro.com/listserv.
--
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.
__________ Information from ESET NOD32 Antivirus, version of virus
signature database 5008 (20100407) __________
The message was checked by ESET NOD32 Antivirus.
<http://www.eset.com>http://www.eset.com
__________ Information from ESET NOD32 Antivirus, version of virus
signature database 5008 (20100407) __________
The message was checked by ESET NOD32 Antivirus.
<http://www.eset.com>http://www.eset.com
----------
I am using the Free version of <http://www.spamfighter.com/len>SPAMfighter.
We are a community of 7 million users fighting spam.
SPAMfighter has removed 1357 of my spam emails to date.
The Professional version does not have this message.
