Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

I recently purchased a Truly Ergonomic keyboard (model 209) that I use both at home on my GNU/Linux machine and at work where - very sadly - I am obliged to use an macbook air sporting the last version of OSX.

While the keyboard is equipped with a few dip switches that allow to change the keycode of the modifier keys to naturally fit the "special needs" of OSX, these are too fragile to withstand daily toggling, and I therefore wanted to remap the keyboard via software, keeping the switches in their default position.

The problem I am currently facing, is that OSX - differently than other OS's doesn't detect the pressure of the two extra keys of model 209:

  • keycode 101 (keysym 0xff27, Hiragana_Katakana)
  • keycode 97 (keysym 0x0, NoSymbol)

I would like to know how to make OSX detect said events or - equally good answer - if there is any other method to get the TE keyboard work properly under OSX (without dip switches, using the CTRL keys as command ones and using the extra two mentioned above as CTRL).

For the records, I already tried keyremap4macbook, pckeyboardhack and ukelele, but none of them allows to achieve what I need.

Many thanks in advance for your help.

share|improve this question
    
Which keys are you referring to? The documentation isn't exactly comprehensive. –  Daniel Beck Jul 11 '12 at 18:14
    
It you are asking about the physical location of the keys on the keybard, they are the lower-left corner (keycode 101) and lower-right one (keycode 97). –  mac Jul 11 '12 at 19:56
    
The keys labeled as control in dip switch 2 off in the quick start guide, and not defined for OS X otherwise? Looks like a strong hint it behaves as designed. –  Daniel Beck Jul 11 '12 at 20:01
    
@DanielBeck - Yes, I know what the kb is designed for, and I linked the quick start guide myself in HTML format. :O My question is indeed "I would like to know how to make OSX detect said events". The keyboard do send the events, the problem is with OSX (surprise, surprise!) and I would like to know it there is some clever guy/gal who managed to find a workaround for that software design limitation... –  mac Jul 11 '12 at 20:26
2  
meta.superuser.com/questions/2125/… meta.superuser.com/questions/3948/… significant community support in both topics, just some unwillingness by the guy running the sites prevents further deletion. –  Daniel Beck Jul 12 '12 at 8:02

4 Answers 4

I dont have the keyboard but interested in one to use with OSX. I read somewhere on Geek Hack one user used Controller Mate ($25) to remap those keys. The Truly Ergonomic documentation also suggests this. I also heard that Truly Ergonomic was supposed to release software to remap the keys.

share|improve this answer

Truly Ergonomic + Mac user here. Controller Mate allows remapping of the left space bar (when the dip switch is set to non-space bar). No other software were able to even detect that keystroke. I would hazard to guess it allows remapping of the two extra keys on the 209 as well.

share|improve this answer
    
Thank you for the info. Do I understand correctly that you are using the keyboard in PC configuration (dip switch #2 == off)? It that's the case, will you have a chance - sometimes - to check if the keypresses are in fact detected (or you have a 207 model?) ? [Regardless: +1] –  mac Jul 22 '12 at 10:05
    
With the new (v3?) firmware, left space sends "AppsKey" aka "Menu", which should be easier to remap. –  Florian Jenn Jun 11 '13 at 8:42

I created a topic on Geekhack.org that explain how to remap internal keycodes used by the Truly-Ergonomic's firmware. That may help you...

share|improve this answer
2  
That's it [although it might be not that easy for non-programmers to get to implement it]. If you will post here your solution (as per SuperUser best practices) I will gladly accept your answer! :) –  mac Jan 9 '13 at 9:41

Did you try creating a private.xml with KeyRemap4MacBook?

97 (0x61) is normally F6, and 101 (0x65) is F9. The Japanese kana key is normally 0x68 though. See KeyCode.data.

Try if any of these work:

<autogen>--KeyToKey-- KeyCode::F6, KeyCode::A</autogen>
<autogen>--KeyToKey-- KeyCode::F9, KeyCode::A</autogen>
<autogen>--KeyToKey-- KeyCode::JIS_KANA, KeyCode::A</autogen>
share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.