Here's one for script enthusiasts, and I would really appreciate it if one
of you out there takes a few minutes to look at it for me.
I use the ControlUp and ControlDown keys extensively in my editing. Most
word processors use these keys for moving by paragraphs instead of just
lines.
But every time I install a new version of JFW, I find the ControlDown key
doesn't work, and I have to go in and fix the default script. It's so
obviously wrong to me that each time I fix it for myself, I have assumed it
will be corrected in the next release. It was still wrong in version 3.2,
and now I have downloaded the new default scripts, and find it is still
wrong, I am moved to raise it. Am I the only one who uses these keys?
I should point out that the scripts for Word specifically handle these keys,
so the problem isn't obvius. But it becomes apparent in editors like
WordPad, or TextPad which I use extensively for text editing, and it is also
apparent in the message editing window in Outlook and Exchange. These keys
are quite common for moving by paragraphs that it makes sense to have them
work right in the default scripts.
The default script for ControlDown makes various decisions depending on what
kind of control we're in, and in general it sends the ControlDown key to the
application, pauses and then reads the current word or current line,
whatever is appropriate for the control. But if none of these applies, the
last choice is SayControl(GetCurrentWindow)), without sending ControlDown to
the application. So if you're in a text or message editor or word processor
for which there is no specific script for ControlDown, when you hit
ControlDown it is not sent to the application, but instead a lot of text is
spoken, and you just end up staying where you are.
The solution is to alter the default ControlDown script by removing the
SayControl(GetCurrentWindow()) line, and replacing it with
{control + down arrow}
sayline()
It is interesting that the default scripts for ControlDown and ControlUp are
quite different in construction, and I can't figure out why. ControlUp
works, but ControlDown doesn't, without this modification. I can't help
thinking even that the SayControl(GetCurrentWindow)) in the ControlDown
script was put in for debugging purposes and has never been removed.
Moving up and down by paragraphs in text editors and message editors has
always been very important to me. I've always been able to fix the problem;
it's the first thing I do when I download a new version of JFW. But if
others agree that it is actually wrong, I'll raise it with HJ so it can be
properly fixed.
CJL
-
Visit the jfw ml web page: http://yoyo.cc.monash.edu.au/~nallan/jfw
