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

Add Skyloong GK68 Pro keyboard. #23621

Open
wants to merge 5 commits into
base: develop
Choose a base branch
from
Open

Conversation

NaturalZh
Copy link

Create Skyloong GK68 Pro keyboard

Description

Skyloong GK68 Pro is an RGB light effect keyboard with 68% keylayout.

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

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).

@github-actions github-actions bot added keyboard keymap via Adds via keymap and/or updates keyboard for via support labels Apr 27, 2024
keyboards/skyloong/gk68/pro/config.h Outdated Show resolved Hide resolved
NaturalZh and others added 2 commits April 30, 2024 11:27
OK, I do it.

Co-authored-by: Drashna Jaelre <drashna@live.com>
@NaturalZh NaturalZh requested a review from drashna April 30, 2024 06:05
@drashna drashna requested a review from a team May 1, 2024 06:27
};
#endif

bool process_record_user(uint16_t keycode, keyrecord_t *record) {
Copy link
Member

Choose a reason for hiding this comment

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

This sort of functionality should really go in the keyboard level, as the default+via keymap should be pristine.

Copy link
Author

Choose a reason for hiding this comment

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

OK, I do it.

}
return false;
# endif
case TO(0):
Copy link
Member

Choose a reason for hiding this comment

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

Not a fan of this. DF would be a better option for this, I think. And worst case, add a layer_clear with it, to clear all the active layers.

Copy link
Author

Choose a reason for hiding this comment

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

If I use the TO(), I can immediately indicate the layer change when I press TO(), but when I use the DF(), I need to release the DF() to indicate the layer change. From the perspective of user experience, the TO() is better than the DF(). @drashna

@NaturalZh NaturalZh requested a review from drashna June 17, 2024 07:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
keyboard keymap via Adds via keymap and/or updates keyboard for via support
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants