![]() In closing, the whole reason I went with the Huntsman Mini over the Corsair tenkeyless keyboard that was in stock was because this keyboard has switches I prefer. Even though their applications might have suboptimal usability, the keyboards can do what I want them to because they do not arbitrarily prevent customization. Seriously why is the macro module SO SLOW? The chinese knock offs are generally on par or better in terms of macros, to boot. While their driver applications look dated, the software is usually faster than Synapse. I would have been better off spending 1/2 the money on one of the chinese competitor keyboards. At this price point it should be able to be totally customized on the hypershift later. It may sound like I'm asking a lot from a tenkeyless keyboard but this thing has onboard profile storage. If I could bind the hypershift layer how I like, WASD would have been my arrow keys.The whole point of the numpad (for me) is the muscle memory and key proximity increases speed and accuracy with numbers. While I could blow 10 of the 12 customizable non-modifier keys on getting the numpad scan codes on the keyboard, it'd be a waste. I use the numpad pretty frequently and the first thing I intended to do was try to franken-bind the numpad numbers to OP[L './ and right shift. I'm retreading some ground from item #3 but this really is the nail in the coffin for me: There is no logical way to replicate the numpad on this keyboard.Again, did no one test this device's usability? My other Razer keyboard flips the LED to green when caps is on. Why does the caps lock key not change color when it is active? Even the cheapest keyboards I've bought have an indicator light.This would obviate the contortion issue with the arrow keys as well. There would likely have been room to put the right side Fn between the smaller space bar and right ALT and the existing Fn key could be another programmable key. That way we could have an Fn key on the left side of the space bar. Given the above issues with arrows and the Fn key, it seems like it would have been great to make a 80% to 60% space bar instead of a full size one.Sleep really should have been assigned to backslash/pipe. I can only imagine how great that is going to be for productivity. Heaven forbid I put a macro on A, S or X and fat finger a key press. Speaking of the keys we can rebind, who's brilliant idea was it to put the sleep button (Fn+Z) anywhere near the keys we can change? Honestly did anyone test this from a practical standpoint? Three of the 12 precious customizable keys circle the Hypershift key of doom.Yet, I do not consider 12 keys to qualify as "Enjoy an extra set of buttons using the Razer Hypershift key". If this were not a tenkeyless board, I wouldn't be here complaining. Not counting the modifier keys, hypershift really gives us 12 extra keys. I'd go so far as to call this misleading. The language used to explain Hypershift implies far more flexibility than the feature actually provides.Instead I have comfortable access to keys I rarely use (PrtScn, PageDn, End), and a date carpal tunnel syndrome when I use the arrow keys. Surely P, L, and ' would have been a better choice, no? This would let us hold Fn with the right thumb and easily use arrow keys. In any case, this is far too awkward to have been widely tested before production. As soon as I want to press the up arrow and other arrows, it is literally painful. If I only want to press a single arrow, these key choices are just suboptimal. Single handed use of the I, J, K and L keys for arrow keys requires a contortionist wrist angle to use, due to the location of the Fn key.I just bought this today and after spending about 15 minutes in Synapse, I regret the purchase.Īside from the valid point the OP brings up (which also infuriate me), I have some general usability issues with the keyboard that could have been done away with if we had complete control over which keys hypershift can modify: I wouldn't be surprised if the technical limitation was "the key caps already have the hypershift icons printed on them". can we get a firmware update that changes this? Is there a workaround that I am unaware of? Rootklm I can't imagine a technical reason for this limitation.
0 Comments
Leave a Reply. |