From: M.W. Poirier
To: xywrite@xxxxxxxx
Sent: Thursday, June 25, 2009 12:08:52 PM
Subject: RE: OT "...greatest keyboard(s)..."
Brian:
No, you are right about Rcontrol::LWin. It works as you stated in
your previous message. I am, at the moment, using my old keyboard
(IBM, Model) and I now have access to a Windows key on a keyboard that
clearly does not have a Windows key. I also modified my laptop,
which does not have a Windows key, and it too works as expected.
Great.
I also am a bit confused about the number symbol. i.e., the "#". (I
see that you do not refer to it the same way in the U.S. You call
it the pound symbol. We here view it as a number symbol. It likely
has something to do with our Fremch heritage.) I know that while using
my newer keyboard, which has a Windows key, I was able to obtain the
same effect with #h as I now get with your command Lwin, but #h did
not work at all
with IBM Model M. So you are likely right when you
say "..."#" symbol is for putting the result of Win key combinations
under a 3rd key...". Where did you come across the "LWin." What does
"L" refer to? "Left"?
Thanks for your help, as well as to Harry.
MWP
--------------------------
On Thu, 25 Jun 2009,
mailto:Brian.Henderson@xxxxxxxx wrote:
> I'm still trying to figure out how this program works (maybe it's just
> me but I don't find the instructions particularly clear).
> I did manage to change my right ctrl key to a functioning Win key using
> "RControl::RWin". I think the technique that uses the "#" symbol is for
> putting the result of Win key combinations under a 3rd key...I think...I
> may be wrong.
>
>
-BH
>
> -----Original Message----- From: Harry Binswanger
>
> Maben,
>
> Yes, I'm sure--I got the syntax from AHK Help and I tested it on my
> system.
> The pound sign is the symbol used to indicate the Win key has been
> struck--e.g.,
>
> #A::Send Winkey-A has been struck
>
> But that's for when you have a Win key. Thank of # as meaning ScanCode
> 15B
> (which is what it is, in hex I think). You have no key that outputs 15B.
> So
> you want to assign some other key (e.g., right-control) to output that.
>
> The correct instruction will work regardless of your keyboard, because
> the
> whole point of it is to reinterpret *whatever* your kbd puts out.
>
> To get things working right, you should use AHK's "keyhistory" function
> to
> look at what is actually being sent and received, at the scancode
level.
>
> Assign keyhistory to some keystroke. I use ctrl-alt-k:
>
> ^!k::keyhistory
>
> The keyhistory window is rather awkward and technical, but if you scroll
> up
> to the headings of each column, you should be able to get valuable info
> from it. (In referring to its output, note that it distinguishes
> key-down
> and key-up).
>
> Let me know if you have problems (you could send me your AHK script for
> debugging here if you wish).
>