Closed lalomartins closed 8 years ago
This is probably because fusion's key code outputs (slightly) different keycodes (ErgodoxEZ used TMK firmware first). QMK's TO is using an additional parameter:
https://github.com/jackhumbert/qmk_firmware/blob/master/quantum/keymap_common.h#L175
Fusion isn't finished (yet), so this is one thing we need to fix.
Basically it should say TO(1,ON_PRESS). What remains is how many keys are in the [0] = KEYMAP
line, it should correspond with the KEYMAP macro. Ergodox has 76 keys, so there should be 76 entries on that line.
Well, I really want to play with my shiny new keyboard ;-) and I have a bit more time, so I'll give this a try. If it works, I'll see if I can submit PRs.
Thanks!
So is it TO(x,ON_KEYPRESS)
, or is it TG(x)
? I tried the former as you said, but then just setting TRANSPARENT
on the same position of the other layer won't switch back. I solved that by putting TO(0,ON_KEYPRESS)
on the other layer, but after sleeping on it I guess it was just mean to be TG
?
It's TG(1) indeed, I got confused. Last work has been done here by the way: https://github.com/ErgoDox-EZ/fusion-rails
GTK, I was confused by the two repos. Thanks!
(BTW as you probably inferred, I got mine working. Joy.)
Well, this is a bit of a problem :smile_cat: I can create a layout with fusion and reactor, but it won't build. Or I can use the Massdrop UI, but then I don't have the mouse emulation functionality. What's a geek to do?
(Use the default map, I guess, but I'm a Dvorak guy, and the software-based dvorak map puts [] in an utterly unusable place.)
Here's the build output; what it looks like to me is that the template in reactor is out of date with the firmware api.