-
Notifications
You must be signed in to change notification settings - Fork 86
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
Feature requests; scroll up/down, rapid fire available for media keys, accessing the default layer from another layer, clipboard. #31
Comments
Yeah, the issues page is the correct place for this, although it's a good idea to put separate feature requests into separate issues. This allows each to be tracked individually.
So, in conclusion, I probably won't be able to find the time to get to 1,2. 3 is interesting in that there should probably be a Fn0 for completeness, but I'm not sure I'll be able to get to it right away. 4 I don't think so. If you really need some of these changes, you may want to fork the code and add it yourself, then submit a pull request. |
We could close this and I could open 4 individual issues...
So I will look into 1 and 2 early June when I have time, if noone looks into this before then. 3 and 4 were things I thought would be nice to have, but I probably won't look into them. |
This is an old issue. #3 was recently added to the firmware. The rest of it was addressed in discussion. |
Mouse scroll up/down buttons.
There are mouse buttons 3, 4 and 5, but no scroll (unless that's what 4 and 5 are, but I wasn't expecting them to be. I could test this, but I have other feature requests as well so I may as well ask : ) ) - Ideally I'd like these to be rapid fire-able.
Rapid fire mode available for Media Keys.
I use the media keys, especially the volume up/down buttons. As such, I would like these to have the option to be rapid fire, as currently there is no option for this and I believe it could be possible. I use rapid fire on the keys I have mapped to backspace, delete, and arrow keys (48 ms min hold time (default is 800), default / 32 ms repeat delay), and as such would like it on my volume control too as I miss not having it. This may also be nice for macros, but that may be hard to add, as it would conflict with the length of the macros, so I don't know if this would be doable.
Accessing the default layer from another layer.
Default layer / layer 0. If I'm on another function layer, would there be a way to get back to the default layer? For example, If I was to have the "Caps" key mapped to "Fn", "W" (Qwerty layout) mapped to "Ctrl", and then I want maybe the "Enter" key mapped to "Fn0", such that I can do something like Ctrl+C without moving my hands from the home row or moving them to somewhere uncomfortable as the bottom left of my keyboard / "LCtrl" is uncomfortable to type. Whilst this is a very specific example, I'm sure there could be other uses for this. I know that the default layer can be changed, but then how would you get to layer 0?
Clipboard.
A temporary copy / paste layer, or a clipboard-style history thing. If (like me) you are using all 10 layers, and then decide you want to move some layers around, whilst the copy / paste function is nice, it isn't as helpful as it could be. Of course, the layers don't necessarily need to be moved around, but it makes it slightly easier to customise the layout if the similar layers are "grouped" (at least in my mind).
Finally, I would like to thank everyone for all their work so far on this project as it makes my one-of-a-kind keyboard possible : )
P.S.: I haven't used Git much, so I'm hoping the "Issues" page is the right place to put this : )
The text was updated successfully, but these errors were encountered: