Problem with mouse doubleclicking

Hey all

Im having a little trouble with my mouse (SteelSeries Ikari Laser).
It keeps doubleclicking from time to time. So far its cost me a lot of gold in overbuying stuff.
The problem is only when Im in GW. When Im on the desktop (windows7) I cant provoke the problem, nor can I in any other game.

Im hoping someone here might have had that problem or know a solution to it

I've had/seen that problem before, but not just in GW. It happened because one of the micro-switches in the mouse became "bouncy" - that is, the contacts close, then bounce open and close again when pressed, essentially causing a double click.
Most (if not all) of the time, when I've encountered that problem, it was a Microsoft mouse and the way I fixed it was to replace the MS switches with switches from a dead Logitech mouse.
I've never seen that problem only in one app or game though - it was always a universal problem.
The only thing I can suggest is to try a different mouse just to find out if it is the mouse causing the problem. There seems to be no way to set a minimum double click speed, but you could check to see if there's a setting to average or smooth mouse response in the GW setup and change the setting (either way) to see if that changes things.
Also, of course, make sure there is no setting in any software that came with the mouse, that does an automatic double click in games. (Btw, there's really no reason to install any mouse driver that may of come with the mouse, so you could try un-installing one if you did.)

My first thought was also that the problem had to be the button/switch.
The mouse I use is SteelSeries Ikari Laser which ofcourse doesnt require installing a driver, however the mouse has features that require a driver.

So far I've reinstalled the driver and its still the same, so to conclude all of this, I've written to SteelSeries to see if they have an answer.

Since theres no real utilities/options in GW to configure a mouse Im gonna go with what you say and my first thought. It has to be the switch, even though I havent been able to duplicate the problem outside GW.