Hey guys. I got the tenkeypad from this page (http://elitekeyboards.com/products.php?sub=leopold,tenkeypads&pid=fc210tpcb) so that I could use it for trainers and games which require input from numpad numbers, not the numbers in row 5 of the keyboard. Unfortunately, the pad registers as the row 5 numbers, which completely defeats the purpose of owning it. Is there a program that I could use to remap the keys to the numpad numbers without also changing the ones on the row 5 of my keyboard to the numpad numbers as well? Sorry if I can't explain the problem clearly, I'm a bit frustrated.
So you can't do Alt-0xxx using this external numpad then?
Hi (real Name of Nixietube),
Yes, that is correct; the number codes sent are not Numberpad codes, but number row codes.
Best regards,
Brian
Yes, they do [still have this issue]. This should be fixed in the next batch in a couple of months.
I've seen some posts where people got "fixed" Leopold tenkeypads. However, I just got this reply back from EK today, so it would probably be safe to wait a bit before getting a Leopold:QuoteYes, they do [still have this issue]. This should be fixed in the next batch in a couple of months.
I've seen some posts where people got "fixed" Leopold tenkeypads. However, I just got this reply back from EK today, so it would probably be safe to wait a bit before getting a Leopold:QuoteYes, they do [still have this issue]. This should be fixed in the next batch in a couple of months.
The new ones are fixed, mine came from S.Korea and it's is perfect, it's just going to take a little while for the stock to filter through to EK. They are great numpads.
The Filco has the same problem. I had one for a while and never used it because of it.
<?xml version="1.0"?>
<root>
<devicevendordef>
<vendorname>Leopold</vendorname>
<vendorid>0x04d9</vendorid>
</devicevendordef>
<deviceproductdef>
<productname>FC210TP</productname>
<productid>0x0176</productid>
</deviceproductdef>
<item>
<name>Convert Leopold Numbers to Keypad Numbers</name>
<identifier>private.leopold_to_keypad</identifier>
<device_only>DeviceVendor::Leopold, DeviceProduct::FC210TP</device_only>
<autogen>__KeyToKey__ KeyCode::KEY_0, KeyCode::KEYPAD_0</autogen>
<autogen>__KeyToKey__ KeyCode::KEY_1, KeyCode::KEYPAD_1</autogen>
<autogen>__KeyToKey__ KeyCode::KEY_2, KeyCode::KEYPAD_2</autogen>
<autogen>__KeyToKey__ KeyCode::KEY_3, KeyCode::KEYPAD_3</autogen>
<autogen>__KeyToKey__ KeyCode::KEY_4, KeyCode::KEYPAD_4</autogen>
<autogen>__KeyToKey__ KeyCode::KEY_5, KeyCode::KEYPAD_5</autogen>
<autogen>__KeyToKey__ KeyCode::KEY_6, KeyCode::KEYPAD_6</autogen>
<autogen>__KeyToKey__ KeyCode::KEY_7, KeyCode::KEYPAD_7</autogen>
<autogen>__KeyToKey__ KeyCode::KEY_8, KeyCode::KEYPAD_8</autogen>
<autogen>__KeyToKey__ KeyCode::KEY_9, KeyCode::KEYPAD_9</autogen>
<autogen>__KeyToKey__ KeyCode::EQUAL, KeyCode::KEYPAD_EQUAL</autogen>
<autogen>__KeyToKey__ KeyCode::DOT, KeyCode::KEYPAD_DOT</autogen>
</item>
</root>
The Filco has the same problem. I had one for a while and never used it because of it.
The Filco has the same problem. I had one for a while and never used it because of it.
the filco shouldn't, it should register as a normal numberpad.
if you use aqua keytest you'll see its actually pressing numberpad then the button on each keypress
http://geekhack.org/index.php?topic=21101.0
I just don't understand why the Leopold is the only numpad with a proper size 0 key :(
I just don't understand why the Leopold is the only numpad with a proper size 0 key :(
I don't understand why so many numpads don't have an equals key.
Whether or not it should is an entirely different matter.
Whether or not it should is an entirely different matter.
;D
There is a separate keycode for them. And Apple's keyboards have had one for decades. That means they should have one. ;)
There are times when it really comes in handy. Oddly enough, that's not while using a calculator, since I prefer RPN. :cool:
The combination of a full sized zero key, an equals key, and Cherry blues is why I bought the Leopold. Being about to work around the number codes problem is why I kept it. :)
:D Please share when you get it working, if it's relatively painless (although I am a software dev, so my "pain" threshold is fairly high), then I'll just pick one of these up.
The Leopold I ordered arrived yesterday. It really does have the problem described by the OP.
An email sent to Elite Keyboards' support confirmed that there is no firmware update. But then, neither could I find any other numeric keypads that use Cherry blue switches. Heck, I found some other very strange limitations in separate numeric keypads along the way. (No equals key?!? What's up with that?!? :eek:) So I had to find a way to make it work.
Long story, short; I'm on a Mac. Elite Keyboards has a utility listed on their site called KeyRemap4MacBook, and its interface is even more awkward than its name. But if you take the time to manually build the necessary xml file, it can remap the keys at a low enough level that no application even realizes the keys have been remapped.
So if you need it, here's the xml file needed to remap those keys using this utility:Code: [Select]<?xml version="1.0"?>
<root>
<devicevendordef>
<vendorname>Leopold</vendorname>
<vendorid>0x04d9</vendorid>
</devicevendordef>
<deviceproductdef>
<productname>FC210TP</productname>
<productid>0x0176</productid>
</deviceproductdef>
<item>
<name>Convert Leopold Numbers to Keypad Numbers</name>
<identifier>private.leopold_to_keypad</identifier>
<device_only>DeviceVendor::Leopold, DeviceProduct::FC210TP</device_only>
<autogen>__KeyToKey__ KeyCode::KEY_0, KeyCode::KEYPAD_0</autogen>
<autogen>__KeyToKey__ KeyCode::KEY_1, KeyCode::KEYPAD_1</autogen>
<autogen>__KeyToKey__ KeyCode::KEY_2, KeyCode::KEYPAD_2</autogen>
<autogen>__KeyToKey__ KeyCode::KEY_3, KeyCode::KEYPAD_3</autogen>
<autogen>__KeyToKey__ KeyCode::KEY_4, KeyCode::KEYPAD_4</autogen>
<autogen>__KeyToKey__ KeyCode::KEY_5, KeyCode::KEYPAD_5</autogen>
<autogen>__KeyToKey__ KeyCode::KEY_6, KeyCode::KEYPAD_6</autogen>
<autogen>__KeyToKey__ KeyCode::KEY_7, KeyCode::KEYPAD_7</autogen>
<autogen>__KeyToKey__ KeyCode::KEY_8, KeyCode::KEYPAD_8</autogen>
<autogen>__KeyToKey__ KeyCode::KEY_9, KeyCode::KEYPAD_9</autogen>
<autogen>__KeyToKey__ KeyCode::EQUAL, KeyCode::KEYPAD_EQUAL</autogen>
<autogen>__KeyToKey__ KeyCode::DOT, KeyCode::KEYPAD_DOT</autogen>
</item>
</root>
For you Windows and Linux/Unix guys, sorry, I don't know of a similar utility for you. Maybe someone else here knows of something.QuoteThe Filco has the same problem. I had one for a while and never used it because of it.
Along the way of working this out, I discovered that the vendor code sent by the Leopold is Filco's vendor code. No wonder the two keypads have the same problem.
Nicely done seriously! I don't think it's possible to do on windows though at least not without fancy drivers.
a couple hours? eeek
(meaning... highly doubtful)
I just ordered one from qtan so hoping it's fixed. Will report back
I just ordered one from qtan so hoping it's fixed. Will report back
I just ordered one from qtan so hoping it's fixed. Will report back
soloz, have you received the Leo from qtan yet? I'm thinking of ordering the black with mx red from him, but I also want to make sure his current batch is outputting the correct codes. I already emailed him, so awaiting an answer but I'm curious if you've received yours yet.
nobee,
What OS are you using at work?
I already posted on the vendor forum, but I'll repost here because I said I would provide an update. Gonna be contacting qtan for a return. I ordered the black MX Red.
Looks like the one I got from qtan is unfortunately printing off the wrong codes even though he said that they should be printing off the correct codes.
I'm going to have to email him for a return now. Unfortunately, I need the correct codes to work with software I use at work. A little disappointing because I did specifically asked him about this before ordering.
Here are all the keys registering from the Leopold FC210TP on Aqua's Key Test.Show Image(http://i.imgur.com/XZ71Csj.jpg)
I already posted on the vendor forum, but I'll repost here because I said I would provide an update. Gonna be contacting qtan for a return. I ordered the black MX Red.
Looks like the one I got from qtan is unfortunately printing off the wrong codes even though he said that they should be printing off the correct codes.
I'm going to have to email him for a return now. Unfortunately, I need the correct codes to work with software I use at work. A little disappointing because I did specifically asked him about this before ordering.
Here are all the keys registering from the Leopold 210TP on Aqua's Key Test.Show Image(http://i.imgur.com/XZ71Csj.jpg)
I'm sure this trouble is caused by the question being lost in translation. The difference is subtle.
this is exactly why I want a Realforce 23UB. It has a DIP switch so that you can have it act like a true NumPad. Also, it's thorprer.
My Goldtouch NumPad suffers from this exact same problem - doesn't send proper scancodes. It's incredibly frustrating.
this is exactly why I want a Realforce 23UB. It has a DIP switch so that you can have it act like a true NumPad. Also, it's thorprer.
My Goldtouch NumPad suffers from this exact same problem - doesn't send proper scancodes. It's incredibly frustrating.
I have a 23U. Works just like a numpad. I've tried the Filco. I didn't check it to see which keycodes it was sending. Even so, it doesn't hold a candle to the quality of the 23U. The difference is night and day. Of course, the 23U is/was 3x the price of the Filco.
thanks alot for the update, nobee.
I already posted on the vendor forum, but I'll repost here because I said I would provide an update. Gonna be contacting qtan for a return. I ordered the black MX Red.
Looks like the one I got from qtan is unfortunately printing off the wrong codes even though he said that they should be printing off the correct codes.
I'm going to have to email him for a return now. Unfortunately, I need the correct codes to work with software I use at work. A little disappointing because I did specifically asked him about this before ordering.
Here are all the keys registering from the Leopold 210TP on Aqua's Key Test.Show Image(http://i.imgur.com/XZ71Csj.jpg)
I already posted on the vendor forum, but I'll repost here because I said I would provide an update. Gonna be contacting qtan for a return. I ordered the black MX Red.
Looks like the one I got from qtan is unfortunately printing off the wrong codes even though he said that they should be printing off the correct codes.
I'm going to have to email him for a return now. Unfortunately, I need the correct codes to work with software I use at work. A little disappointing because I did specifically asked him about this before ordering.
Here are all the keys registering from the Leopold 210TP on Aqua's Key Test.Show Image(http://i.imgur.com/XZ71Csj.jpg)
Looks like NUM Lock is off. What happens if you turn it on ?
I already posted on the vendor forum, but I'll repost here because I said I would provide an update. Gonna be contacting qtan for a return. I ordered the black MX Red.
Looks like the one I got from qtan is unfortunately printing off the wrong codes even though he said that they should be printing off the correct codes.
I'm going to have to email him for a return now. Unfortunately, I need the correct codes to work with software I use at work. A little disappointing because I did specifically asked him about this before ordering.
Here are all the keys registering from the Leopold 210TP on Aqua's Key Test.Show Image(http://i.imgur.com/XZ71Csj.jpg)
Looks like NUM Lock is off. What happens if you turn it on ?
Num lock was on. I toggled it on and off, but the key test doesn't highlight it for some reason. Although, it does on my Das. Turning Num lock off just turns on the arrow keys.
It has to send the regular number keys if its own NUML is on but the system NUML is off (in my Scorpius 32 firmware FN+NUML will turn on local NUML.)
It has to send the regular number keys if its own NUML is on but the system NUML is off (in my Scorpius 32 firmware FN+NUML will turn on local NUML.)
I don't understand this. Why would the system NumLock need to be on to send the keypad number codes from a separate device?
Actually that's the way it's supposed to work, any other way would be insane.
The only time something should even pretend to know anything about its own status is if its a fully programmable keyboard being run from a teensy or something and you have different layers.
The only time something should even pretend to know anything about its own status is if its a fully programmable keyboard being run from a teensy or something and you have different layers.
That's actually a strike against the OS trying to be too smart. It limits the ability of designers and end-users to come up with creative and flexible solutions to their own workflow.
The other common strike against OS overaggressiveness is the point of this very thread—using a separate numeric keypad. There are two setups where this is common: With a notebook where the keyboard does not have room for a separate number pad, and TKL keyboards. (In my case, my TECK falls into the latter category.) In both scenarios it's common for the keyboard design to include an embedded numeric keypad to make major number entry easier. For such an embedded number pad to be appropriately useful there needs to be a number lock feature (so your left hand can be on the paper to keep track of where you are).
So now you have a problem. When the number lock on the keyboard is off so you can type, and that number lock is system-wide, does that now mean the numeric keypad you've added must not be permitted to send numeric codes? That is the situation we have now.
The result is that the keyboard and keypad designers must come up with a workaround. One option is to have the number pad send the number codes for the top row numbers instead of the numeric keypad codes. But there is software that needs to perform different functions based on whether the number was typed on the keypad or the top row. One example is the music notation software I use, and I can tell you, that needs to be that way.
Another option is to toggle the systemwide number lock when passing the number code. But that can run into timing issues. There's a reason good keyboards have N-key rollover: because when things are happening fast, events can become so close that they overlap and interfere with each other. Toggling the system number lock in that situation can lead to unexpected results if the lock is still on when a second key's event is processed, which can happen with multiple devices.
You mentioned one advantage to a systemwide state: keeping the state of multiple devices in sync. But think about it. When does this make sense? When each device is different? (As in the notebook/TKL keyboard + number pad) Or when each device is the same? (As in two dedicated number pads.) If the latter, would the end user always want them in sync? Or put this way, why would the end user add a second number pad if they wanted both of them to do exactly the same thing?
Another possible reason to use a systemwide state is to simplify keyboard design. But if you think about keyboards, they always have to track the number lock state anyway to turn the LED on and off. So I don't see any technical reason to not have each keyboard track it's own state(s). Heck, it's done for caps lock.
So is there an MX keypad that operates 'properly', as in sends keypad codes?
I should've googled (or red the description) before I ordered a leopold numpad... :( Mine don't work with numpad codes either...
http://imgur.com/rXhkbgF
http://imgur.com/XKvnPSJ
http://imgur.com/Ka9UyI2
Anyone know if the Filco numpad sends numpad codes?
Sorry to bring up an old thread - but does anyone own one of the new Leopold numpad? (as seen here: http://www.geekkeys.com/leopold-fc210tp-21-key-numpad-grey/). I'd really like to get one but only if it sends numpad codes.
I bought my Leopold numpad a while back and have the same issue.
I tried using HID Macros because it's USB device specific, and received limited success: http://www.hidmacros.eu/
My problem with HID is that it doesn't map to every possible key.
I bought my Leopold numpad a while back and have the same issue.
I tried using HID Macros because it's USB device specific, and received limited success: http://www.hidmacros.eu/
My problem with HID is that it doesn't map to every possible key.
Care to share your exact code for getting this to work (or as close as you could get)? Or maybe a brief how to? I have used auto hot key before, but HID macros, (now LUA Macro) is much more dense, and their "how to" or "getting started" doesn't really help me understand it. I'm lost and could use some guidance. Thanks!