-
Notifications
You must be signed in to change notification settings - Fork 298
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
Illustration of default keymap? #20
Comments
Ya... I realize it's kind of hard to find... There's a keymap illustration ("firmware--layout.html") in each of the .zip files containing the binaries -- see the Downloading Binaries section of the readme. (I'd put the direct link here, but it may move some day). There's also the Massdrop web UI for making layouts here (which has a default layout you can navigate too). I know this isn't what you meant, but it is a good way to visualize things :) . Zalusithix (from GeekHack) has another UI here, though it still doesn't have the ability to generate .hex files. Or if you're feeling particularly adventurous (and you're familiar with unixish stuff) you could generate your own! lol. See this thread, especially the last few posts, if you're going to try that -- it may be difficult, since I never really meant it to be used outside my own unix-based environment, but at least one other person's got it working (on Ubuntu I think), so it's definitely possible. |
@benblazak as we talked about this before, I think keeping your layout generator around and up to date seems to be a great idea. I know it can get complicated as people start adding macros and modifier combinations to the layouts. As I'm adding/optimizing my layout I clearly can see how useful it can be. |
:) . I plan to keep it around, if I can, as part of the documentation. I do need to make it a little less brittle though. Also, the new C layout format in rev. 2 will be much easier to use, I think, since there's only one matrix instead of three. |
hmm, nice idae to simplify the layout matrix, I need to read the new rewrite more carefully since I couldn't figure out how the functions for keys are assigned in the new rewrite... |
Take a look here. Please keep in mind though that nothing in rev. 2 is completely finalized, especially since I haven't actually tested (or even compiled) any of the code yet (almost there!) |
Is there a picture of the default keymap floating around somewhere?
The text was updated successfully, but these errors were encountered: