I'd be rather against it, based on my experience with LGS (it behaved slightly differently under different conditions, making it even more confusing to use). Unless you make it absolutely clear, what device is currently active and how to switch to the other one.CM Bram wrote:Would it also be appriciated to implement more products into 1 software? For example if you have aCM keyboard and CM mouse that you now need 2 software programm's. Would it be a good added value to have into 1 software (like logitech)
I'll repeat myself, but I prefer the way it is in the Roccat Linux driver project. The core is shared, but each product has a separate configuration dialog, e.g. pyraconfig for Pyra and savuconfig for Savu. Each could be launched from a context menu on one icon in the systray.
And now for something completely different... Please, if you use any pictures, use vectors. Combined with standard GUI widgets, it would make the software easy to use on screens with different dpi.
For me, a perfect scenario would be a well-documented core driver (hopefully not just a binary blob) with public API for each common OS... You could have a flashy front-end for gamerzzz, command-line folks could make a simple CLI interface, I'd develop a simple Plasma widget for KDE Plasma, front-end for OS X would probably look different etc.
