Add support for K70 Rapidfire (non-RGB) 0x1b3a

[hevanaa]

This is now done against testing branch. I've also added the KB in question and the K70 LUX non-RGB to the IS_MONOCHROME macro. Hopefully this is correct.

[hevanaa]

Hmm, something went wrong there.

[hevanaa]

OK, think I solved the merge conflict (testing branch had changed after I forked it).

[tatokis]

From my understandint, the difference between a device being (!IS_RGB) or (IS_RGB && IS_MONOCHROME), is that the latter, while leveraging the RGB protocol, can allow for per-key lighting.
From Corsair's site I can see that both of these keyboard do support it, so we should be okay. Just need someone to test it.

Looks OK to me.

[hevanaa]

I've compiled and tested with my K70 LUX non-RGB. The Rainbow demo stopped working. The Trippy demo still worked. I guess the IS_MONOCHROME is no good then?

[hevanaa]

Couldn't get it to work at all with !IS_RGB. I'm removing them both from IS_MONOCHROME for now.

[hevanaa]

There must be some difference with the Strafe model (that has the IS_MONOCHROME macro) and at least this K70 LUX (non-RGB). Most things work in the GUI, except that pressing the Change Color button freezes the interface, but this happens both with if it is in IS_MONOCHROME and not (and it has always been like that with this model).

[tatokis]

pressing the Change Color button freezes the interface That's a Qt bug, we have info about it in the readme.

[ghost]

Cross-reference to #86.

Works for @koanya who owns such keyboard. See #55 (comment).

[tatokis]

My guess is these keyboards discard the colour packets, so it should be safe to add them for now.