I'm using Multiplicity 4.05. I am using one Primary and one Secondary computer in Seamless mode.

I experience periodic losses of connectivity of up to one or two seconds. This is not the problem I need help with, however. At default settings, if the mouse/keyboard are on the Secondary computer during one of these connection interruptions, control returns to the Primary machine, and can then be returned to the Secondary at will.

However, I prefer to enable Settings > Seamless Mode Switching > Control Switching Based on Mouse Movement  > Prevent Computer From Switching Unless Shift is Held Down

If this setting is enabled during a connectivity loss, the mouse/keyboard no longer generate inputs on either Primary or Secondary computer either during or after the connection interruption. Only ctrl+alt+delete works (which sends to the Primary), and the only way I can resolve the situation is to sign out of the Primary computer, killing the Multiplicity process that way. On logging back in and reconnecting, everything works normally again until the next interruption.

I suspect this is a bug, given how specific the steps to reproduce are, and that the connectivity problems do not impact Seamless mode unless the "Hold down shift" setting is enabled, but does anyone have any suggestions for working around this problem?

I need to prevent accidental switching between environments, and the "Shift" setting seems ideal. Are there other ways to restrict this effectively until this apparent bug can be addressed?

I am not interested in paying an additional $50/yr on top of Object Desktop to gain access to Pro, which would allow me the alternative of hotkeys to switch between computers, or utilizing KVM mode to operate the Secondary computer in a window.

Thank you.