Mouse snapping issue

Hi all

Been playing with ISBoxer the last few nights and loving it. I do have a slight issue though that I'm unable to resolve. I'm not sure if it's a bug or if I have set something up wrong (although it's a very simple setup).

The screen setup was done through the wizard. It is a simple single large window (1) taking up around 70%ish of the screen, with 2 more below this. Nothing fancy.

Code:

--------------------
|                  |
|        1         |
|                  |
--------------------
|  2   |   3  |    |
--------------------


Sorry for the crude example. I'm not sure if it's related to my issue, so including it just to be sure.

I have the ` key setup to swap between clients. I often only have 2 clients launched, so it just spawns between them.

With 2 clients launched, the issue: When I press the client swap key (`), often the mouse snaps with the current client to the new position. This does not always happen, but is much easier to replicate if the mouse is moving.

Repro instructions:
Launch 2 clients with the window layout above (don't know if related to the issue)
Map a key to switch the clients (I use `)
Turn on broadcasting in Window 1, if not enabled
Move the mouse and press the client swap key in window 1. Moving the mouse almost always causes the issue for me. Keeping it still means it's less likely to happen (and why I think it might be a bug)
The mouse has now snapped to the lower part of the screen (position 2) and needs moving to the main window (1) again.

Is this a bug, or have I set something up wrong?

Many thanks

Sadly there seems to have been an update and now things are even worse.

With the same setup as above, pressing the ` key to swap between clients does one of the following:

[*]Nothing
[*]It changes correctly as it should
[*]A client window vanishes

Sometimes clicking the client manually causes it to temporally fix or cause other issues.

Most of the time when attempting to use the shortcut to swap between clients the client window flashes in the task bar, but the swap doesn't take place.

Is there an official way to submit bugs? These issues mean that I can't use ISBoxer at all without vastly changing my setup (which kinda defeats the purpose)

Regards

[lax]

Most of the time when attempting to use the shortcut to swap between clients the client window flashes in the task bar, but the swap doesn't take place.

This is probably less related to ISBoxer.

The reasons for the taskbar flash are defined by Microsoft as follows...

The system restricts which processes can set the foreground window. A process can set the foreground window only if one of the following conditions is true:

The process is the foreground process.
The process was started by the foreground process.
The process received the last input event.
There is no foreground process.
The foreground process is being debugged.
The foreground is not locked (see LockSetForegroundWindow).
The foreground lock time-out has expired (see SPI_GETFOREGROUNDLOCKTIMEOUT in SystemParametersInfo).
No menus are active.

An application cannot force a window to the foreground while the user is working with another window. Instead, Windows flashes the taskbar button of the window to notify the user.

Source: http://msdn.microsoft.com/en-us/library/windows/desktop/ms633539(v=vs.85).aspx

It's pretty difficult for me to guess off hand what it mght be, but you probably have other software running that is somehow causing this. You could get me "Diagnostics for game crashes" from the Help menu in ISBoxer and then I might be able to guess. If you haven't rebooted though, that could potentially clean up some software that's running and doing something strange though. (I understand this might "only happen with ISBoxer"... the trick is to determine why it happens for you but not everyone else)

often the mouse snaps with the current client to the new position. This does not always happen, but is much easier to replicate if the mouse is moving.

Well you've got broadcasting on, so messages are being sent from client A to client B that it needs to update the mouse position. If you happen to switch at just the right moment during that processing, you could get this issue... I'm not sure there's anything I can suggest for the short-term other than to not be moving the mouse at the instant you switch windows