Test development-changes with all devices about cue.net

[RobertBeekman]

Hey, the test application crashes on startup because the AbstractCueDevice is calling InitializeLeds(); in the constructor. When creating a CorsairMouse the InitializeLeds(); method is referencing MouseDeviceInfo but that's not set until after the base class has been constructed, resulting in a null reference

[DarthAffe]

facepalm I even commented that warning away ...
Please try again with the latest version - it should be fixed

[RobertBeekman]

Haha now you know what it ment ^^

It looks pretty good, both mouse and headset update (headset a bit laggy like in #47 but that's a CUE issue)

With the mousemat it seems the bottom LEDs get colored a bit different from the side LEDs, is that intended?

It looks like this: http://i.imgur.com/elYzyGZ.png

For Artemis I wrote some code that maps a brush to the mousemat by reading the pixel colors of the sides (left, bottom and right), maybe that's useful for you too: https://github.com/SpoinkyNL/Artemis/blob/development/Artemis/Artemis/DeviceProviders/Corsair/CorsairMousemats.cs#L56 feel free to rip some stuff out of that if it's any good :)

EDIT: Effect stacking works really nice too, great job on that

[DarthAffe]

Well, since the mousemat provides coordinates for the LEDs, I'm using them. I don't get why the top and bottom corners aren't vertically aligned, but that's corsairs decision. I think I'll leave it like that.

[RobertBeekman]

Ah yeah makes sense to do it with their coordinates, ima do that too, that indeed leaves the implementation with Corsair

[DarthAffe]

Since I just released the version I consider this as done for now.
Thanks again for the help :)