geekhack
geekhack Community => Keyboards => Topic started by: fateswarm on Sun, 25 August 2013, 08:14:37
-
So, CM QF TK has this "amazing" feature of having the arrow keys competing with the num pad on what should be enabled at the same time. It's normally fine for text typing, since normal touch typing technique shouldn't bother with arrow keys or numpads anyway.
But when I find the arrows comfortable and at the same time want to use the arrow keys, I wonder if there is a way to do it with a "shifting" key.
So, is there a way, to have the arrows on, but, when I press a shifting key (even Shift itself might do) to only then turn the numpad on?
edit: Title's parenthesis.
-
PS. I just found a funny violation of its NKRO: ctrl+numlk doesn't let numlk work.
PPS. I should better have a more accurate title.
-
You could do this with AutoHotkey:
F12 & NumPadUp::Send 8 ; hold F12 as the modifier to get 8 from up
+NumPadLeft::Send 4 ; hold either shift as the modifier to get 4 from left (cf LShift, RShift, RCtrl etc)
The & syntax allows for non-modifier keys to act as modifiers; the Send approach prevents shift from "sticking" during the remapping
-
You could do this with AutoHotkey:
F12 & NumPadUp::Send 8 ; hold F12 as the modifier to get 8 from up
+NumPadLeft::Send 4 ; hold either shift as the modifier to get 4 from left (cf LShift, RShift, RCtrl etc)
The & syntax allows for non-modifier keys to act as modifiers; the Send approach prevents shift from "sticking" during the remapping
ok, how about a non-windows solution
-
Why, what OS are you running? OS/2 Warp?
-
You could do this with AutoHotkey:
F12 & NumPadUp::Send 8 ; hold F12 as the modifier to get 8 from up
+NumPadLeft::Send 4 ; hold either shift as the modifier to get 4 from left (cf LShift, RShift, RCtrl etc)
The & syntax allows for non-modifier keys to act as modifiers; the Send approach prevents shift from "sticking" during the remapping
ok, how about a non-windows solution
Outside of windows, the world is pretty bleak in this regard.
I'm not sure about OSX, but last time I checked there was nothing remotely as powerful as AHK available.
Linux (which I use for probably 3/4 of my computing) is a complete nightmare for things like this -- the input handling is done ad-hoc by a bunch of layered systems written by different people over the course of decades. You can end up in situations where your keybindings work only in terminals, or everywhere but your web browser, etc.
-
You could do this with AutoHotkey:
F12 & NumPadUp::Send 8 ; hold F12 as the modifier to get 8 from up
+NumPadLeft::Send 4 ; hold either shift as the modifier to get 4 from left (cf LShift, RShift, RCtrl etc)
The & syntax allows for non-modifier keys to act as modifiers; the Send approach prevents shift from "sticking" during the remapping
Interesting. That worked only if the numbers on the keypad were on. Shift + 2 actually goes 'down' instead of 'up' but it's generally a good start.
Edit: Wait a second. It didn't work at all. shift+2 goes 'down' here on the browser anyway.
-
I've very rusty on autohotkey. Is that code complete, or does it need to be wrapped around other code?
-
It works for me — I just tested it again, with an .ahk file that contains only those two lines.
With num lock turned off, F12+NumPadUp becomes 8, and shift+NumPadLeft becomes 4. Those are the only assignments it makes.
You're right in that the TK has a different numpad layout than a normal keyboard, and I was looking at my own. However, you should still find that pressing the exact combinations I stated, will work. The idea was that you'd type out all the rest if it did what you were expecting.
-
Not working, tried x86, x64, adding the '#NoEnv' etc. lines on top..
No behavior that alters anything at all. I wonder if autohotkey works at all.
-
Ah, now it's working. NumPadUp is instead Up etc. (I figured in raw input window).
Thanks for the help Daniel Beardsmore!
-
Oh man.. they've crippled it. "Down" on num pad actually sends Zero twice. It's not a "DoubleZero", it's practically two 0s. That means 0 can't be both left and down! And the main reason of the problem is that Enter key is disabled completely when arrows are on, it sends no events at all.
Unless one does some hackery and translates 'double 0 quite close in succession' to 'down' but I don't know if it's even possible.
EDIT: Hrm, unless I call "1 5 2 3" "left up down right" and call it a day.
edit: Oh that won't have "END!". J H.C CM..
-
lol …
There's a text expansion feature in AutoHotkey, but I don't think you could tune the timing to only pick up on automated keystrokes.
I think you need to put a new controller into the keyboard :) I wonder how hard it would be to adapt the custom Filco controller project?
-
I got a satanic idea: 3, 00, ., Enter being the arrows. Though it looks weird to the eye and Enter should have a slightly different feel on it, being bigger.
-
Bah I give up. Shift+. insists of sending a 'Delete' that isn't overridden (??). Whatever. It seems they did everything possible to make it impossible.
edit: Oh jesus, it doesn't even send an event on '1' or '3' when in arrows mode either, just like with Enter.
-
Wait a second. All this time Shift + 8, 4, 6 and 2 were sending an up, left, right, down, just like ancient keyboards.
Though I always found 'down' being that far unintuitive. And Shift+5 insists of sending a NumpadClear that appears unmappable to a Down.
-
I guess what you need(ed) was a program that tells you what's being pressed. Aqua's KeyTest is a good one: you get to see what key the computer sees as being pressed.
-
I can see the events on autohotkey's window. The machine doesn't send events at all in some cases. e.g. Enter is totally dead on the numpad when arrows are on (Plus, 1 and 2 as well).
Also that's a bit blurry in my understanding but some events appear 'overriding' autohotkey. e.g. shift + . on numpad mode appears to always send an non-override-able Delete event.
-
You can always go low tech :p works on any keyboard and any OS ^_^
Just joking (or maybe not :p )
-
http://deskthority.net/marketplace-f11/qfr-and-filco-105-controllers-t6193.html
I doubt Kitten Paw would fit a QuickFire TK, but you get the idea.
-
Nah, I'll just live with it until it dies or I find it interesting enough to get another device.