Bug?

[MiRai]

Here's how it all went down. DKs have Death and Decay bound to a key with send next click. So I press the keybind [so all windows now have a mouse cursor] and then press the mouse repeater key and the mouse cursor goes away . Now the mouse repeater is [b]opposite. When the cursor shows in all windows it's not really doing it's job. When the cursors go away in my slave windows it's really there.

Not sure if this is a known bug or not but I figured I'd point it out. :)

[Lax]

Technically, it's doing exactly what you told it to -- turn on mouse repeater for those windows, then toggle it which turns it off for those, and on for others ;)

I believe this is one of those cases where the desired behavior would be indeterminable, and I chose to leave it as it is. For example, would the user prefer it to turn OFF mouse repeater for ALL windows? If so, then he MAY also intend for a key to be pressed again on specific windows to toggle a targetable spell off, but not always. Or, would the user prefer it to block state changes until the send next click is completed? But that can also get in the way. If you use a 2-step repeater on/off instead of the default toggle hotkey via the profile, you can always make sure the state is the same on all windows, though.