Cursor release problem with vertical monitor configuration
from 
Stardock Forums
Stardock Forums
Normally I run my Multiplicity machines side by side, but I just experimented with a vertical monitor configuration (secondary above the primary) for the first time today. It works fine for regular Windows applications, but when a full-screen DirectX game (such as World of Warcraft) is active on the secondary machine, it will not release the mouse cursor to the primary as long as the game has focus. Alt-tabbing out of the game allows the cursor to transition across monitor boundaries as normal, but alt-tabbing back in prevents it again.
If I reconfigure the machines back to a side-to-side layout (by just dragging the monitors around on the grid), or if I place the secondary machine below the primary instead of above, cursor release works properly again. It seems as if the software may simply not be testing the bottom boundary of the screen for cursor release, only the sides and the top.
I've verified this behavior on two different secondary machines connected to the same primary. I've also experimented with the undocumented "Machine configuration is stacked vertically" switch in the advanced settings (on both primary and secondary), and it has no impact on this particular glitch.
As a sidenote, is it intended behavior that the Multiplicity client on the primary machine must be unloaded and restarted before advanced grid configuration changes will take effect? The monitor configurations do not seem to change until that is done, regardless of how long I wait after closing the settings box.
If I reconfigure the machines back to a side-to-side layout (by just dragging the monitors around on the grid), or if I place the secondary machine below the primary instead of above, cursor release works properly again. It seems as if the software may simply not be testing the bottom boundary of the screen for cursor release, only the sides and the top.
I've verified this behavior on two different secondary machines connected to the same primary. I've also experimented with the undocumented "Machine configuration is stacked vertically" switch in the advanced settings (on both primary and secondary), and it has no impact on this particular glitch.
As a sidenote, is it intended behavior that the Multiplicity client on the primary machine must be unloaded and restarted before advanced grid configuration changes will take effect? The monitor configurations do not seem to change until that is done, regardless of how long I wait after closing the settings box.