-
-
Notifications
You must be signed in to change notification settings - Fork 40.7k
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
keymap for idobo #6250
keymap for idobo #6250
Conversation
…ally started from
} | ||
return false; | ||
break; | ||
case ADJUST: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Doesn't look like this keycode is used in the keymap, so this case
can be removed, along with the ntry in the custom_keycodes
enum.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
which keycode, I'm using each of the layers? Not sure if I needed the lower/raise/adjust thing here.. or if it's in base qmk now and I can discard in my keymap. (taken from a different keymap example, but can't say which, as it was too long ago.)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This whole case
block here - the keycode ADJUST
and the layer name _ADJUST
are separate things, and you can still access the adjust layer by holding LOWER
and RAISE
simultaneously - that's what the update_tri_layer()
stuff above is all about.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh!, Since I don't have a key mapped to "ADJUST" your saying the adjust case should be removed? The update_tri_layer with the lower/raise on it's own will take care of going to the Adjust layer when both are pressed.
Should the QWERTY = SAFE_RANGE, be removed from custom_keycodes also?
Thanks!!!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, actually, I didn't notice 😄 But you should then add the = SAFE_RANGE,
to the LOWER
keycode instead, otherwise the enum will start at 0 instead of the custom keycode range.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
modified, thanks!!
removing unnecessary part, copied from different keymap Co-Authored-By: fauxpark <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me. 👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
* greenshadowmaker keymap for idobo xd75 massdrop * remove uneeded config.h * corrected format to match convention instead of xd75 where I accidentally started from * fixed errors and added arrows bottom right to match my other layouts * updated readme * right arrow fix * Update keyboards/idobo/keymaps/greenshadowmaker/keymap.c removing unnecessary part, copied from different keymap Co-Authored-By: fauxpark <[email protected]> * added suggested changes * removed unneded elements
* greenshadowmaker keymap for idobo xd75 massdrop * remove uneeded config.h * corrected format to match convention instead of xd75 where I accidentally started from * fixed errors and added arrows bottom right to match my other layouts * updated readme * right arrow fix * Update keyboards/idobo/keymaps/greenshadowmaker/keymap.c removing unnecessary part, copied from different keymap Co-Authored-By: fauxpark <[email protected]> * added suggested changes * removed unneded elements
* greenshadowmaker keymap for idobo xd75 massdrop * remove uneeded config.h * corrected format to match convention instead of xd75 where I accidentally started from * fixed errors and added arrows bottom right to match my other layouts * updated readme * right arrow fix * Update keyboards/idobo/keymaps/greenshadowmaker/keymap.c removing unnecessary part, copied from different keymap Co-Authored-By: fauxpark <[email protected]> * added suggested changes * removed unneded elements
* greenshadowmaker keymap for idobo xd75 massdrop * remove uneeded config.h * corrected format to match convention instead of xd75 where I accidentally started from * fixed errors and added arrows bottom right to match my other layouts * updated readme * right arrow fix * Update keyboards/idobo/keymaps/greenshadowmaker/keymap.c removing unnecessary part, copied from different keymap Co-Authored-By: fauxpark <[email protected]> * added suggested changes * removed unneded elements
* greenshadowmaker keymap for idobo xd75 massdrop * remove uneeded config.h * corrected format to match convention instead of xd75 where I accidentally started from * fixed errors and added arrows bottom right to match my other layouts * updated readme * right arrow fix * Update keyboards/idobo/keymaps/greenshadowmaker/keymap.c removing unnecessary part, copied from different keymap Co-Authored-By: fauxpark <[email protected]> * added suggested changes * removed unneded elements
Description
Keymap updates for my idobo kemap
Types of Changes
Issues Fixed or Closed by This PR
Checklist