CKB - New Feature Requests

[mattanger]

For anyone who wants to suggest new features for the ckb driver. Please leave a reasonably detailed description of your idea and reasoning as to why it should be added. Thanks!

[frickler24]

Hi @mattanger, today I read that you have opened that clone. Thank you for that!
My recent development on the ckb were the macro definitions in the client and server.
They are integrated in your version, because they had been promoted to the testing-stage in the ccMSC-branches.
In combination with an other programmer, who added variable delays between keystrokes in the daemon (as I see now, you integrated it as ccMSC/ckb#437), I implemented a GUI for that. My pull-request was too late - ccMSC was offline at the time.

Here is a screen shot, the difference is just the green radio-buttons letf hand.
When recording a G-Key-macro, the delay between keystrokes while typing is stored.
You have three choices afterwards: Replaying the macro as typed with the delays recorded,
playing the macro without any delay or playing the macro with default-delays as you can select in your current implementation.

So my two questions: Are you interested in that development?
If yes, can you give me a hint how to deal this with git, because the PullReq was relative to the git-history from ccMSC?

Another point: I'm german speaker (so my bad english). Are you interested in a german version of the GUI and the README.md?

best regards, Lutz

[mattanger]

Hi @frickler24, thanks for getting in touch. I think that this improvement is definitely something that we'd like to see in this version. My keyboard doesn't have G-Keys, and I, personally, haven't run any to any issues in regards to macro's. I do remember seeing that thread where some of the issues related to this were discussed, and I see how why it may be needed.

I could be missing something, I also haven't really looked either, but are these GUI changes in ccMSC/ckb#437? Because we haven't merged that PR in yet. Otherwise, the best thing to do is to get your repo up to date with ours, and then submit a PR for your GUI changes.

As to German translations, I'm not opposed to making ckb-next as accessible as possible if you'd like to make a translation.

[tatokis]

Regarding the best thing to do is to get your repo up to date with ours, I would like to add that you should base it on our master, and not the testing branch, as that is currently being left behind until we can get to a stable state.

[randominternetuser]

Hello,

I'd also like to see support for Corsair Void headsets, they have lighting and several buttons I would like to work under linux. Currently there is very limited support for these headsets under Linux.

Thanks.

[batchpert]

Hi regarding the macros with delays between them. I really like that as for certain games if you have text within your macro then it doesn't normally pick up all the text before it registers the enter key. I don't have windows but I'm guessing that this feature is available in that and i know that it is available for logitech keyboards. So it would be great if at some point this could be added!!!

[batchpert]

Also a new feature that i was a thinking about was like a sort of snake (sorry was the best way i could think of describing it). But as in you set like a pattern say going around the letter keys and then it follows it at a constant speed. I know this is quite similar to the pin wheel but that doesn't go at a constant speed and wouldn't be able to follow something that doesn't just go in a circle/oval shape without lighting up more than one key.

[Camoleopard]

Hi,
I would love to see support for newer devices such as the Corsair Harpoon RGB Mouse, the void headsets, and any other devices not currently supported.

[SyntaxualSugar]

I would love to be able to use a combination of mouse buttons for a command. For instance: One the m65 pro we have a "sniping" button the side. I would like to use that and the two top buttons to change dpi. That, combined with having the "sniping" button set to its default function, and the top buttons set to window spread and workspace spread would be a wet dream.

[frickler24]

@FlutterFox That's quite difficult.
First we need some more coding for macro handling. I tried to use a M65 with its buttons to send keyboard-macros, but I could not find a clean way to implement it because of the internal structure of the client software (device handling).
But I still think about it...

[slugger7]

Hi
First of all thank you for forking and continuing with this amazing project that personally works better than the Windows version provided by Corsair.
Something that v2 of CUE has is that you can layer your effects to apply the effects to certain buttons but not others. Almost like CSS (for clarification Cascading Style Sheets) where changes where there is a rule for a style on an object but it can later be override with another CSS file.
So in the Animation section: the order in which the animations appear matter. (Top layer will override all other layers when active (type lighting over a rainbow pattern for instance currently does not work or I am not using it correctly)

[slugger7]

@FlutterFox I did something similar to that using a different function that basically creates a macro that is then mapped as a bash script to that button. I think the program that i used was xdotool just go have a read on what that does. Best of luck if you still battle then give me a PM and ill give you a more in depth guide once I figure out what i did way back when.

[tatokis]

If I understood correctly, I think what you're looking for is the different blending modes.

[tatokis]

Forgot to add, you can select which keys an animation applies to, by selecting the keys from the keyboard displayed in the UI.

[slugger7]

@tatokis I think I have figured it out thank you