I've been a Multiplicity user for over a year now. When I first got Multiplicity (v1.02, I think) I was able to "dual box" playing World of Warcraft more effectively than I can now with version 1.05 which I recently upgraded to.

My "problem" is that I think I was relying on an unintended behavior that was recently fixed in Multiplicity.

In the past, when I was controlling the copy of WoW on my secondary machine and I pressed Mouse3 (the button I use in Ventrilo as the "push to talk" key) it would still activate Ventrilo on my primary machine so I could chat with other people in my raid group. This stopped working when I upgraded to Multiplicity v1.05.

I imagine both Multiplicity and Ventrilo have a global hook to capture mouse and keyboard input. I'm not sure how this works specifically, but when an application installs a global hook and captures a keyboard or mouse event, they have the option of not "bubbling" this event up to the rest of the applications on the computer. What I would like to happen is for Ventrilo to capture events first (before Multiplicity gets they mouse or keyboard event) so my push to talk hotkey works no matter where my mouse cursor is currently located. Dual boxing is tricky to begin with, so having to move the mouse back to the primary machine when I walk to talk really makes things more difficult. I finally decided to ask this question here because I figure that someone from Stardock would know a lot more about global windows hooks than me and let me know how to solve this problem. Would this be due to a change in the Multiplicity code? How does Windows determine what application's global hook gets the keyboard or mouse event first?