2 ms·
The issue I see with this is that the {} keys are usually just shift + []. Whereas the Fx keys are often pressed together with some combination of ctrl / alt /
by vladvasiliu 5y ago
The issue I see with this is that the {} keys are usually just shift + []. Whereas the Fx keys are often pressed together with some combination of ctrl / alt / shift. So not having the row, that would add another key to the combo. Or make it a two-step process.
I actually have the same frustration as GP. I usually want a 75% keyboard so that I can have my mouse close to it, and since I don't ever use the numpad, that works out great.
But I don't care about the keyboard being actually small, so I would absolutely love some of those "macro keys" like on the gaming keyboards and also direct access to media keys.
Yes, I know you can have layers and combinations, and it might not even be that much slower (or at all) with one of those compact keyboards, but I find it much more comfortable to be able to only push one key with one finger.
I sometimes use my keyboards while doing something else besides "full-on typing" with both hands on the keys. Granted, in those cases I wouldn't be bothered by a full-width keyboard, but having two keyboards is just not something I'd consider practical.
- Symbiote 5y agoI compromised with a similar keyboard without an F-row. I configured it so pressing 1 and Q together¹ sends F1. I use this far more often than Fn+1, since I can do 1Q singlehanded/singlefingered. ¹ Actually 1 and ", because Dvorak.