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

[minidox] Four-Key Chords aren't the same as two Two-Key Chords in sequence #17

Closed
2 of 4 tasks
davidagross opened this issue Dec 2, 2019 · 1 comment
Closed
2 of 4 tasks
Labels
enhancement New feature or request

Comments

@davidagross
Copy link
Owner

Feature Request Type

  • Core functionality
  • Add-on hardware support (eg. audio, RGB, OLED screen, etc.)
  • Alteration (enhancement/optimization) of existing feature(s)
  • New behavior

Description

It'd be great if we could use the Row 1 SFT, CTL, ALT, and GUI combos with other combos, but right now we can't. Four-Key Chords require a combo term that appears too long to be feasible.

@davidagross davidagross added enhancement New feature or request help wanted Extra attention is needed labels Dec 2, 2019
@davidagross davidagross removed the help wanted Extra attention is needed label Dec 2, 2019
davidagross pushed a commit that referenced this issue Nov 27, 2022
* bastardkb: cleanup blackpill configuration

Fixes #17

* bastardkb: fix splinky configuration

The pinout of the splinky changed between the last beta batch, and the
production one. This commit updates the keyboard definition to support
the new pinout by default, while offering backward compatibility.

Define `SPLINKY_BETA_PINOUT` to build the firmware with pre-production
pinout.

Fixes #15

* bastardkb: add support for STeMCell

* Update scylla/tbkmini/skeletyl outdated readmes

* bastardkb/dilemma: enable circular scroll

* bastardkb/dilemma: add initial version of the `via` keymap

* bastardkb/dilemma/assembled: add new keyboard

Fixes #20

* bastardkb/dilemma: remove elite-c

* Initial support for the Dilemma 3x5+3 Assembled RGB

* Address code review comments

* Address more comments

* Address review comments

* Address more nits

* bastardkb: split splinky-based keyboards to distinguish between Splinky v2 and v3 pinout
@davidagross
Copy link
Owner Author

This is self-resolved with (maybe) the pull from upstream, and multi-combos appear to register properly as long as the keys are not shared.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant