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

New keymap for ID75 - paryz #19350

Merged
merged 7 commits into from
Dec 20, 2022
Merged

Conversation

FilipParyz
Copy link
Contributor

Description

It's just a new, personal keymap for ID75 with layer indication and customized RGB matrix.

Types of Changes

  • Core
  • Bugfix
  • New feature
  • Enhancement/optimization
  • Keyboard (addition or update)
  • Keymap/layout/userspace (addition or update)
  • Documentation

Issues Fixed or Closed by This PR

  • None

Checklist

  • My code follows the code style of this project: C, Python
  • I have read the PR Checklist document and have made the appropriate changes.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • I have tested the changes and verified that they work and don't break anything (as well as I can manage).

keyboards/idobao/id75/keymaps/paryz/config.h Outdated Show resolved Hide resolved
keyboards/idobao/id75/keymaps/paryz/keymap.c Outdated Show resolved Hide resolved
keyboards/idobao/id75/keymaps/paryz/keymap.c Outdated Show resolved Hide resolved
@FilipParyz
Copy link
Contributor Author

@waffle87 Thank you for the review, I'll fix those issues whenever possible :)

@FilipParyz FilipParyz marked this pull request as ready for review December 17, 2022 13:23
@FilipParyz
Copy link
Contributor Author

I think I should be ready with all those changes. I've updated my installation of QMK_MSYS and fixed the keymap for both version of the keyboard :)

#include QMK_KEYBOARD_H

#ifdef RGB_MATRIX_ENABLE
led_config_t custom_led_config = { {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You know, you could just move all of this to the keyboard_post_init_user function, as:

    g_led_config = { {

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Well, yes I guess I could. I believe that's what the compiler will do anyways, to optimize it.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Extremely unlikely -- it's only going to have side effects after keyboard_post_init_user(). Prior to that, the keyboard-supplied values will be present.

I'll wait to see if you want to change things before merge -- your call.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yup, thank you for waiting, changed it. None of the changes made are breaking, so I think we can go ahead :)

@drashna drashna requested a review from a team December 17, 2022 19:58
@tzarc tzarc merged commit ae94be9 into qmk:develop Dec 20, 2022
@FilipParyz FilipParyz deleted the feature/id75_paryz_keymap branch December 20, 2022 18:35
omikronik pushed a commit to omikronik/qmk_firmware that referenced this pull request Jan 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants