Showing 1 of 74 conversations about:
View Full Discussion
So... macOS compatible or not? Please...
Just received mine. Using with MacBook Pro 15" (late 2013) Mac OS X 10.11.3 El Capitan. A Thermaltake Poseidon Cherry MX Blue Keyboard is also hooked up.
Short Story: definitely usable, but not everything works.
1) the first thing you have to do after plugging in is press "Num Lock" or else nothing will work and you will have to unplug it. Can work around by setting dipswitch 3 to On to lock the Num Lock switch to sometimes work as backspace (like in Excel 15.18) or nothing (Safari as I'm typing this).
2) 00 key doesn't do anything. Doesn't matter if dipswitch 2 is On or Off.
3) "=" key seems to press (according to Keyboard Viewer) all at the same time: "<option> `-z-n-e-u-i" and types a "16" or backspace, depending on the program. (yeah I know, doesn't make sense.)
4) Dipswitch 1 has a function to convert <tab>, <BS>, <shift> to cut, copy, and paste. Doesn't work.
Bottom line: still usable, I can deal with the two nonworking keys. Key press feel is great. I'll be using this instead of the NewerTech bluetooth keypad, which still works, but I really don't like the key action.
thank you for all the specifications given... it really is a nice numpad, but it is incredible that it is not prepared out-of-the-box for MacOS. I am still waiting for a Leopold numpad in greens or clears... waiting and waiting.
I have had one of these for several years. I use OSX. No problem.
There's a problem if, I think, you turn numlock off? But I've disabled that through DIP switches.
Been through several keyboards with the 23UB and still keep it on hand. A number row is a painful way to input digits.
Have you guys tried Karabiner-Elements? It might fix the bug as it did with my HHKB that had no multimedia controls working on Sierra.
Thanks for sharing these details. Looks like I was over in the other drop a year go and missed this. (https://www.massdrop.com/buy/topre-realforce-numpad-with-custom-bingecap/talk/295579)
I've had the Realforce 23UB for a while and I'm also on a Mac. Some thoughts and replies from my own use:
2) The 00 key has always worked fine for me, as long as num lock is enabled.
3) When the = key is pressed, the OS interprets 3 key press and 3 key release events:
Because the OS interprets a split-second Option key press, Keyboard Viewer also shows the Option key as pressed for a split second. Whenever the Option key is pressed, keys with combining characters are shown in orange (namely [ ` e u i n ] on a US-layout keyboard), as shown in the following screenshot:
4) I keep all 4 DIP switches in the off position, and I keep num lock enabled. In this configuration all keys but the = key input the labeled keystroke.
5) Like any Topre product, this numpad is a dream to type on. The big problem for me is that somewhere between the device and Mac OS, keystrokes don't get registered quickly enough. If I type fast then a few keystrokes get lost, as if they had gotten trampled in a stampede. Unfortunately this issue is significant enough in my use that I can't type with the numpad reliably.
Topre doesn't make products for Mac, so I think it's amazing that there is any compatibility at all. Topre's Realforce keyboards work better with Mac than their numpad does. But the numpad does work, which is remarkable on its own.
I have done some further testing and want to update a couple of the points I mentioned. Plus there is a new issue to report. But overall this is good news for using the numpad with a Mac.
3) To put it simply, when the = key is pressed, the Mac interprets two modifier+key commands: Option-Keypad 1, Option-Keypad 6. The Option modifier has no effect on keypad numbers, so digits 1 and 6 are simply input.
It is possible to assign a different function to the = key using a macro/automation tool called Keyboard Maestro (https://www.keyboardmaestro.com/)—my favorite Mac application. Create a macro that is triggered by Option-Keypad 1, and choose any output, such as Keypad = or any other character. Then create a second macro that is triggered by Option-Keypad 6, and set that macro to do nothing. Now the = key performs a normal, useful operation—it works like a charm.
5) I've found that the problem with keystrokes not getting registered quickly enough is due to num lock. I had always kept num lock enabled in order to use the 00 key, but when I tried disabling it, the keystrokes registered more quickly. With num lock off, keystrokes no longer get lost. This was my biggest problem with the numpad, but now that it's gone the numpad is usable again.
6) The reason I finally tried using the numpad extensively with num lock off is that num lock on this device causes a problem in macOS Sierra. When I connect to the numpad to my Mac, num lock is enabled by default. If I turn num lock off and back on again, the numpad inexplicably sends the "decrease screen brightness" command to my Mac repeatedly, reducing my screen brightness to 0. Num lock stays on after that and can't be turned off, so I must unplug the numpad to get my screen back.