Search the Community
Showing results for tags 'shift'.
UPDATE: UPDATED QUESTION ABOUT BYPASSING MODIFIER/SHIFT ISSUE LISTED IN NEWEST POST. SEE THERE FOR UPDATE. I AM RUNNING ON A MAC COMPUTER AND AM TRYING TO BYPASS LIMITED FUNCTIONALITY OF MAC ICUE SOFTWARE. PLEASE SEE BELOW. System Info: 2018 Macbook Pro running 10.15.6 Catalina 6-Core 2.9 GHz Intel Core i9 Radeon Pro 560X 4 GB GPU Hi, I sent a ticket to corsair support about this but in the case they don't get back to me I'm going to post this here too because I am extremely exasperated. I am having an issue with the scimitar elite; I am only trying to do one thing: Bind my middle mouse button, to shift. That's it. I want my middle mouse button to behave as the shift button, and to modify all my side buttons accordingly. I.E., when I press middle mouse button, and side button 1 (mapped to normal 1 on keyboard, not numbed 1), it registers as shift + 1. I cannot figure out how to make this work in the software, I have tried the following, but it will range from just not working to completely crashing my computer. It seems like a pretty simple thing to have such dramatic effects on my computer, but that's software, so I digress. Probably helps to explain that I am trying to use this as a modifier button for wow, so that essentially I have access to shift on my mouse and don't have to worry about triggering it with my left hand. Tried all of the following in the "Actions" Tab of iCue. - Tried using a macro that presses and releases shift. Figured out this does not work, because it doesn't function as a modifier button but only as a short keystroke of shift. - Tried searching for shift in the various lists that they have in iCue, could not find it (or control, alt, anything of that nature which I was hoping to map to other mouse buttons) anywhere - Tried mapping shift as a keystroke under middle mouse button, but upon doing so, not only did it not work, but upon pressing the middle mouse button after this mapping, every single time, my computer froze, and I had to restart it, every single time. I don't know if I'm just an idiot, if I'm missing something very obvious, or if there's something just wrong with the software/there are limitations I don't know about, but it seems absolutely ridiculous to me that something as simple as this is so difficult. I read about people attempting much more sophisticated and complex macros than assigning shift to the middle mouse button. Seems to me it would be one problem if I could get it to work as shift but not with the other mouse buttons, but I can't get it to work at all. Isn't it kind of conspicuous that all of the modifier keys are absent in the keybinding section of the software? Is there some computational limitation I'm just missing here? Like seriously man, I am not asking for much out of this mouse. Like I have all the side buttons assigned to numbers, and at the bare minimum, I want the middle mouse button to perform as a shift key. That's it. Nothing else. Forget control, forget alt. I will take just the shift. It doesn't seem like it should be this difficult, but, once again, maybe I'm just missing something super obvious. Is it a configuration issue? Am I not "assigning" the shift button properly? Because if there's another way it's just not very obvious, at least not to me. What the concerning thing really is for me is that it's crashing my computer, button functionality aside. Like I'm pretty careful not to do stuff to my computer that's sketchy, or will damage it. And I would not thing assigning the "programmable mouse buttons" to press a standard button on a computer keyboard would lock up my entire system. Anyway, I am very very frustrated, if that was not already obvious. I just really want to resolve this issue because it seems like it should be very simple and that does not seem to be the case. Like I'm just really baffled that such a simple function is so damn complicated to get right. If you're reading this Corsair, please just make the modifier buttons readily available in iCue and preconfigure them to work properly, because I imagine that would be a lot easier for people than people potentially breaking their computers. Alright, rant finished. Please for the love of God, if you know the solution to this problem, I'm banging my head against the wall here trying to figure this out. But help would be much appreciated. Maybe I'm just a noob but help me out please and thank you <3
I created 2 color profiles -- one is the "Default" color profile and then a "shifted" color profile. While in the "Default" color profile, I set the Left Shift assignment as "Left Shift, Mode switching" where the mode switching switches to "shifted" profile while pressed and reverts back to "Default" profile when unpressed. I did a similar thing to Right Shift. However, I noticed that when holding down the shift keys, while the color profile shifting works as desired, but the shift functionality is lost. So when I do a SHIFT+P key sequence, I only get is "p". Is there any right way to do the mode switching while keypress without losing the shift functionality? My keyboard is a Strafe RGB Brown if that matters.
My new Strafe RGB MX Silent is a great keyboard with great colors. But I have two concerns regarding 1) high key sensitivity, and 2) dim punctuation symbols. Are there any keycap options or adjustments that would address these? Details: 1. Pushing a key down by a tiny amount, like barely a millimeter, seems to activate it. The keys also feel light for that first millimeter. I end up pressing the "d" key by accident just by resting my left fingers on the keyboard. I think pressing a key should require more downward travel or more downward force. 2. On any key with two symbols on it, like the number/punctuation keys, the backlit bottom symbol is too dim to see well, even at the brightest setting. So on the 3# key, the 3 is bright and the # is too dim. On the single/double quote key, you can barely see the double quote symbol at all. The top symbol is the “non-shift” character, which is counterintuitive (on most computer keyboards it's at the bottom), so I guess they’re trying to highlight it. But it’s a problem for me. Strangely, the photo on the box shows the top and bottom symbols at almost identical brightness (hello Photoshop) So it's a bit misleading, not that I noticed the box anyway. If there's a way to rectify these issues with new key caps or mechanisms, especially the sensitivity, I'd love to know. Thanks!
After setting up the M65 mouse, was so impressed with the power of CUE, I went all in for a keyboard also. Until now I'm forced to ask... Does CUE really lack the most basic macro functionality imaginable? I just want to assign a text macro to Control-E. That's it. It would just type an email address. And CUE can't handle that!? Searched around a bit and found this Tutorial: Switching Modes by Modifier Keys, but if I'm reading it right (hope I'm not) it's essentially a worthless technique. It basically says (for my case), create a dedicated profile only for the Control key. Then within other profiles, assign the Control key to switch to the Control profile as long as the key is held down. The massive problem with this approach is, because you have taken over the normal functionality of the control key, all of the control key shortcuts in all of your apps become completely disabled. The tutorial says the way to fix this is to write down a list of every control key shortcut key you'll ever want to use in all of your apps, and recreate a macro for it from scratch within the new control key profile you've just created. Are you kidding me? Not only is that a ridiculous waste of time, what if you ever want to install a new app on your system? Every time you get a new app, you should figure out what built in shortcuts you need to recreate from scratch? Oh, and btw, go through the same process all over again if you want to assign a macro for any Alt key combo. And again for Shift-Alt. And again for...well, hopefully you can see the problem. Simple key modified macros are some of the most basic functionality any power user would want in a keyboard, and this is a train wreck. Has anyone heard if Corsair is planning an update relating to this?