several improvements for mitosis:datagrok #1960
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This requires a corresponding change to the mitosis wireless firmware: reversebias/mitosis#10
This is experimental, but compiles and seems to work correctly.
…d code instead of [, .] [? !], using [, ?] [. !] greatly simplifies the code needed to perform the shifted-key switching. (And keeps , and . on the same keys that they are under qwerty.) also: layout improvements for symbols
need to see if the corresponding changes needed in the keyboard-level code is okay.
|
Cool! Thanks :) |
kgwong
pushed a commit
to kgwong/qmk_firmware
that referenced
this pull request
Nov 26, 2017
* mitosis/datagrok: reduce features from rules.mk * mitosis/datagrok: make both layer keys neighbor shift * mitosis/datagrok: (no-op) tweak some comments * mitosis/datagrok: set baudrate to 250k This requires a corresponding change to the mitosis wireless firmware: reversebias/mitosis#10 * mitosis/datagrok: move design description from code comment to a readme * mitosis/datagrok: new layout, new shifted keys, efficient LED code This is experimental, but compiles and seems to work correctly. * mitosis/datagrok: whoops, move readme.md * mitosis/datagrok: a minor layout improvement simplifies custom-shifted code instead of [, .] [? !], using [, ?] [. !] greatly simplifies the code needed to perform the shifted-key switching. (And keeps , and . on the same keys that they are under qwerty.) also: layout improvements for symbols * mitosis/datagrok: make my code conform to QMK style guidelines * mitosis/datagrok: TODO note for layout table in README * mitosis/datagrok: remove led_set_user until i figure out other changes need to see if the corresponding changes needed in the keyboard-level code is okay. * mitosis/datagrok: simpler layer indicator * mitosis/datagrok: undo change to keyboard baud; make it in my layout dir. * mitosis/datagrok: apply same punctuation hack to qwerty layer * mitosis/datagrok: enable qwerty layer toggle * mitosis/datagrok: update readme
akatrevorjay
added a commit
to akatrevorjay/qmk_firmware
that referenced
this pull request
Apr 3, 2018
* 'master' of git://github.com/qmk/qmk_firmware: (291 commits) More "oscillope" keymap fixes. (qmk#1982) Improved README of yuuki and added RGB commands (qmk#1983) restructure converters (qmk#1825) qwerty_code_friendly: configurable left thumb Migrated most code from keymaps to userspace (qmk#1980) Small ergodox config fix and update. Update and move around drashna keymaps (qmk#1976) make it easy to customize logo image add pgm_read_dword for Infinity ErgoDox 333fred layout update (qmk#1971) Pete's 40th XD64 Layout Ergodox EZ and Atreus 42 key dvorak layout updates (qmk#1964) Correct the rules.mk documentation for auto shift. Fix RGBLIGHT startup color (qmk#1975) adds indication up to layer 7 restore default mode/color if no 0 color adds per-layer rgb color option to ez update gh60 info add gh60 info.json several improvements for mitosis:datagrok (qmk#1960) ...
LovesTha
pushed a commit
to LovesTha/qmk_firmware
that referenced
this pull request
Jul 24, 2018
* mitosis/datagrok: reduce features from rules.mk * mitosis/datagrok: make both layer keys neighbor shift * mitosis/datagrok: (no-op) tweak some comments * mitosis/datagrok: set baudrate to 250k This requires a corresponding change to the mitosis wireless firmware: reversebias/mitosis#10 * mitosis/datagrok: move design description from code comment to a readme * mitosis/datagrok: new layout, new shifted keys, efficient LED code This is experimental, but compiles and seems to work correctly. * mitosis/datagrok: whoops, move readme.md * mitosis/datagrok: a minor layout improvement simplifies custom-shifted code instead of [, .] [? !], using [, ?] [. !] greatly simplifies the code needed to perform the shifted-key switching. (And keeps , and . on the same keys that they are under qwerty.) also: layout improvements for symbols * mitosis/datagrok: make my code conform to QMK style guidelines * mitosis/datagrok: TODO note for layout table in README * mitosis/datagrok: remove led_set_user until i figure out other changes need to see if the corresponding changes needed in the keyboard-level code is okay. * mitosis/datagrok: simpler layer indicator * mitosis/datagrok: undo change to keyboard baud; make it in my layout dir. * mitosis/datagrok: apply same punctuation hack to qwerty layer * mitosis/datagrok: enable qwerty layer toggle * mitosis/datagrok: update readme
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
?and!, keeping more punctuation and quotes on base layersI'm concerned that my changes for the use of an 8Mhz Pro Micro controller might not be appropriate for the
keymapssubdirectory. They are more of a hardware option that can be applied to the higher level keyboard files; they could be useful for boards using the other keymaps too. But I was unsure about the preferred way to set up a toggle for a hardware variant like that. Happy to implement recommendations either for this PR or as a follow-up.