davidagross / qmk_firmware Goto Github PK

Command-control swap is the key thing here. Is the OS detection? Or just one hand's EEPROM is for one and the other is for the other?

Home-End and PgUp-PgDn is the other big one.

And then I guess the Fn keys as well.

Feature Request Type

• command-control
• home-end
• pgup-pdgn
• Fn keys
• Fn lock

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.

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

Right now it's really confusing for PGDN to be "left" and PGUP to be "right" especially when shuttling through open tabs with Ctrl+PG(DN/UP)

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

Not clear what should be on the ADJUST and what should be on SYS but there's a lot more room now after starting to resolve #4

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

The chord for Shift-(Lower->Tab) should work for Shift-Tab no matter how it is pressed, etc.

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

Right now these are just a pain to do and should be easier...maybe part of a movement layer.

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

With ten keys, each one can play one of these songs after chording into some sort of song later.

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

This issue may be obviated by a real movement layer, but when mousing or otherwise using only one hand, the left hand doesn't have Space and the left hand doesn't have Ctrl.

We could have lower and raise bring the opposite thumb near the layer key so that a pointer-thumb combo is the thumb from the other hand? Or maybe the home-row mod-taps would also handle most of this...

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

No idea how this is going to work. Some kind of chording to get into and out of the layer? And the ergonomics are rough

some cute ways to put on caps lock while I still don't really remember where mine is haha

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

Merging in more or all of @dustypomerleau's mod-taps would help with one-handedness in #3 and moving CTRL away from the thumb would probably lessen high-severity typos.

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

I can't remember why this didn't work really.

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

RAISE and LOWER had different movement styles to try them both out, I think the DXCV cluster has won out over the SDFG single row.

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

This just needs to be played with given all the new room there is after starting #4

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

These pay the bills in my daily .NET development, so maybe they should be more central.

Feature Request Type

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

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

definitely while trying to add #12 i want to learn more about a piano key mode, maybe 12-tone or microtonal or ... whatever!

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

Right now these are just a pain to do and should be easier...maybe part of a movement layer.

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

Maybe some of those middle, three finger combs I haven't started using yet.

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

I want this macro pad to flip tables without switching anything (or too much) on the available laptops in the family.

it's looking like I'd really like to have more one-handed operation of this keyboard while mousing, drinking coffee, etc.

if the thumb clusters were symmetric, then maybe we could get to more layers with just one hand.

Part of this might be switching Z and ? to mod-taps for SHIFT instead of the bottom row of combos.

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

Right now it's nav-nav-alt-tab and isn't a chorded combo.

This would also be fixed with #17

By using esc-grave (https://docs.qmk.fm/#/feature_grave_esc) we might be able to make some more room int he combos or SYM later.

When these layers can lock properly, the combos would still be really useful on these layers.

Describe the Bug

I will often still shift a character instead of adding a space. Not sure if the mod-tap timing or permissive hold or interrupt rules are the best approach, or if moving shift off of the super common space, like before, is best. We could try making that NAV again? Or swapping the CTRL and SFT thumb mods? No easy answers here...