Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

mouse keys and massdrop configurator? #2

Open
inkthink opened this issue Dec 29, 2015 · 9 comments
Open

mouse keys and massdrop configurator? #2

inkthink opened this issue Dec 29, 2015 · 9 comments

Comments

@inkthink
Copy link
Contributor

Are the mouse keys or hyper keys available with the massdrop configurator or does that require C?
Also, will using the massdrop configuration tool to alter the base layer override the special layers that are included by default?

@ezuk
Copy link
Contributor

ezuk commented Dec 30, 2015

That does require C. And yes, using the massdrop configurator will override the entire firmware -- nothing is left behind.

Are you familiar with the firmware repository at https://github.com/jackhumbert/qmk_firmware/tree/master/keyboard/ergodox_ez ? Getting started is not as daunting as it seems!

@inkthink
Copy link
Contributor Author

Yes, I've been pouring over the configurators for a couple of weeks, as time allows.
I was glad to find that keymap_default.c and the code seems straightforward at first glance.
I was getting ready to try forking it, actually.
I got as far as looking up step three gcc compiler and discovering the Mac download (AVR MacPack) link is broken.
I haven't yet gotten to hunt for alternatives, but it got me wondering if I might get a much faster start with the massdrop configurator. My customized Kinesis layout for the thumb cluster is firmly memorized and I'm reluctant to retrain temporarily so the EZ's been sitting mostly unused.

P.S. Thanks for the encouragement to try it. I plan to eventually, even if I do throw something basic together with massdrop for now.

@sethherr
Copy link
Contributor

@inkthink - you should use homebrew to compile avr

It's easy:

brew tap osx-cross/avr
brew install avr-libc

Then you can just cd into the ergodox directory and

make clean
make KEYMAP="yourkeymapname"

sethherr added a commit to sethherr/qmk_firmware that referenced this issue Dec 31, 2015
From discussion [here](zsa/docs#2) it became clear that this information should be more available.
@inkthink
Copy link
Contributor Author

Thanks, that's what I was looking for. I'm looking forward to using it. Meanwhile i installed a temporary/testing layout using the massdrop configurator. That was very easy. I did not use the eep file mentioned in these docs, since the link was broken, and the qmk repo doesn't mention it. It worked just fine without it. i'm looking forward to improving my layout with code, but at least now I'm using my keyboard... literally now, to type this. :-)

@sethherr
Copy link
Contributor

Thanks for the heads up about the firmware.eep broken link. It's been fixed

@ezuk
Copy link
Contributor

ezuk commented Feb 20, 2016

Okay, this worked. Interesting...

On 20 February 2016 at 17:23, Eric-L-T [email protected] wrote:

Hello, World!


Reply to this email directly or view it on GitHub
#2 (comment).

@inkthink
Copy link
Contributor Author

inkthink commented Mar 2, 2016

Testing my first full layout now. I find the mouse keys handy... since my mouse broke. I also use caps lock sometimes, which I have mapped to layer 1. I would like to incorporate LED's and found the following instructions for it, but I'm not sure where to place it in the keymap:

if (host_keyboard_leds() & (1<<USB_LED_CAPS_LOCK)) {
  ergodox_right_led_3_on();
}

@ezuk
Copy link
Contributor

ezuk commented Mar 2, 2016

That looks like a macro - I suggest opening an issue over at the qmk repo with this question, lots of action there :)

@eltang
Copy link

eltang commented Mar 2, 2016

@inkthink Take a look at the matrix_scan_user function in the default ErgoDox EZ keymap!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants