Support for Alternative Layouts
This is a summary of how alternative layouts have been supported by kits such as Colevrak and Homing. It is not a discussion of alt layout performance and development, but if that interests you I highly recommend starting with Pascal Getreuer’s A guide to alt keyboard layouts (why, how, which one?). It’s a concise and comprehensive overview with links to some great sites that go deeper. He also has a separate Links about keyboards page. The Keyboard layouts doc he recommends explains layout goals and metrics in detail, summarizing the alt layouts discussed here as well as more than one hundred others. Sculpted-profile The majority of custom keycap sets are sculpted-profile (Cherry, SA, MT3, KAT, etc. - more on profiles generally here) so let’s start there. Because each row has a unique keycap shape, alt layouts require a unique keycap for each legend that moves off its QWERTY row. At first there were two The Dvorak layout was patented in 1936 by August Dvorak & William L....
Apr 23, 2024
1. The configurator @ https://config.qmk.fm/#/tokyo60/LAYOUT_60_hhkb is pretty great. The configurator is missing a default keymap for Tokyo60, so click on each on-screen key and press the corresponding physical key on the board. Hopefully this will be corrected over time. Default key map is there, no worries. 2. I used the MO(1) macro for the function key to trigger a momentary toggle to layer one. - I spent a lot of time looking for a non-existent FN key in the configurator. - Make sure you keep PAUSE somewhere in your keymap, mine is on layer 1. 3. Read the docs on docs.qmk.fm and build your keymap. 4. Click 'Compile' and then 'Download Firmware' to copy your new keymap firmware to your machine. 5. Download and install QMK Toolbox, binaries available for Mac and Windows. 6. Click "Open" in QMK Toolbox and select the firmware file ending in ".hex". The correct microcontoller is "atmega32u4", which I found defined in the QMK Tokyo60 source code. 7. Put your Tokyo60 into boot loader mode using L_SHIFT+R_SHIFT+PAUSE. The default layout uses FN+p for PAUSE. 8. You will see 'DFU device connected' if your keyboard toggles to bootloader mode. 9. Click the 'Flash' button in QMK Toolbox and wait for a device disconnected message. 10. Test out your new keymap! If your keymap doesn't work or the magic boot loader L_SHIFT+R_SHIFT+PAUSE stops working, don't despair! Get out your trusty Philips screwdriver and take the bottom plate off your keyboard. With the keyboard upside down, the purple reset button is on the right hand side in the middle of the board. With QMK Toolbox running, push and release the reset button and you should see a device connected message. Make sure you have left and right shift available in your base map as well as PAUSE. Here is my working keymap, feel free to grab it and make it your own. https://github.com/JnyJny/tokyo60_keymap This guide is replicated here too: https://github.com/JnyJny/tokyo60_keymap/tree/master/firmware
edit: followed the instruction above and i could flash successfully but it seems like i keep getting the default key layout.
I am not sure if the compile process is working perfectly for mine but I keep getting the default layout after flashing. This is so frustrating. If anyone can help, please let me know. I will email you the json file which I have prepared.
I have flashed a DZ60 firmware before and never had any problem.
Can anyone add on to this? Trying to figure out how to program the default Fn key when I flash...
https://www.youtube.com/watch?v=7RH-1pAbjvw&list=PLZlceRZZjRugJFL-vnenYnDrbMc6wu_e_&index=2 https://www.youtube.com/watch?v=VR53Wo9Z960&list=PLZlceRZZjRugJFL-vnenYnDrbMc6wu_e_&index=1
This is what I had in mind to work on my physical keyboard.
I really think Default Toyko60 layout should been provided by the person who sold it.
- if done correctly, you will hear an audible system alert as if a USB device has been unplugged (that's your keyboard going into bootloader mode).
If you are in bootloader mode, In Zadig you will see ATMEGA32U4DFU as your device. You will see USB ID 03EB:2FF4. Install driver 'lilusb-win32'. Once that runs, now move over to QMK Toolbox. If you've already created your layout/firmware HEX file, you can now flash your firmware. That was really it. I've used QMK Toolbox for other keyboards. I hadn't run into this much of an issue previously. All in all, this is what fixed the issue for me.