Keymap Layering/Shifting with Assigned Key (Like Hypershift in Synapse for Keypads) #688
Replies: 2 comments 5 replies
-
I am also looking to do this. |
Beta Was this translation helpful? Give feedback.
-
Well there is no specific feature for that. But I am wondering do we need that? I think this is already possible. You can just create multiple mappings for all the keys you want to change in the second layer:
this should behave the same as having right shift switch to a different "layer" or whatever you want to call it. Just add a mapping for each key you want to have different from the normal layout. |
Beta Was this translation helpful? Give feedback.
-
First of all, I think it's great this program exists, because it fills a hole that companies refuse to fill coughrazercough, or at least are slow to do so. - However, despite that this exists, it still might lack some key functionality that is really important to the potential of a keypad.
Though, this post is partially a question, because there might be a way. - But if not, it's a suggestion or request.
The main question is: Is it possible to assign one key to shift the entire layout (or selected keys) to a different layout or programming/mapping?
I've looked around but couldn't really find anything. But considering you can input a lot of stuff, there might be some way I don't know about.
If you don't know what I mean: It's basically turning one key on the programmed device into a modifier, which would turn the programming of the device to what would practically be a different profile, except it's within the same profile and just another "layer", kind of like what a common keyboard does with its modifiers.
This feature is called "Hypershift" in Synapse, but it was already a feature for Belkin's Nostromo SpeedPad (which then became Razer's Nostromo, turning into Tartarus and Orbweaver), except it had a more generic name like "shifting" or "toggling" the layers or profiles. - You could still toggle through at least three "layers/profiles" in Synapse, but "Hypershift" is very specifically to swiftly "shift" to another layer for all keys and back when you release the modifier-button.
The reason this is useful is because of course keypads have way fewer keys available, in this case about 20, which isn't very different from half the main part of a keyboard, but that can be a bit limiting. - The "layering" of keymaps helps at least doubling their functionality, and the advantage is that you don't even need to move your hand or fingers. - What's more is that you can "group" the types of functionality to these "layers", such as your normal navigational keys on the main "non-shifted" layer, but then put things like item-keys (such as the numbers) on the "(Hyper)shifted" layer, or whatever you like.
I had been using the Belkin Nostromo SpeedPad n52 this way since 2004/2005, and because it wore out I had to move to Razer's Tartarus (Pro) in 2019/2020. But now that I've moved to Linux, and there's zero Linux-support for Synapse (although tech-support told me they're working on it, albeit without any time-frame), a lot the functionality of the device is gone as it was all powered by Synapse. - It works, but all I can do is straight-forward single-layered mapping, unless now I'll be told that you can program Input Remapper to do more than I realize of course. - It just slashes the versatility down critically for me, enough to feel handicapped, because I don't even know how to play games with a keyboard anymore, and I even used it outside of games for productivity. Not to mention that Synapse also switched profiles dynamically on-the-fly. - So I'm basically back two decades in terms of interfacing with my computer, unless I go back to Windows.
So any suggestions or even new features for this would be greatly appreciated, because I can't wait around for Razer to do anything about their software, even the Windows-version of it. - Thanks for reading, the consideration, and this program so far.
Beta Was this translation helpful? Give feedback.
All reactions