Stuck key issue
from 
Stardock Forums
Stardock Forums
I am using the most recent version of Multiplicity PRO as is 10 other tech's in my group. We like your product, but really cant purchase any more licenses until the underlying issues are resolved...
As you probably already know, if someone were to hit cntrl+alt+del to unlock a secondary machine by accident (forgetting the cntrl+alt+bkspc), multiplicty delivers some odd behavior. Sometimes the result is that you cannot click on icons, sometimes alt or cntrl will just not function.... The remedy is to hit all of the previously used keys a couple times on the primary machine and then navigate back to the secondary’s. I have also found that at times the scroll wheel of my mouse will not work until I return to the primary, use it and then swap back to the secondary.
For this to be used in production within our firm, we need this bug worked out. There should be some error checking routines you could include to clear the buffer of stuck keys or input device actions in general. I was told by the sales rep that the bugs I had encountered in the shareware version would not be present in the live, yet I still have this issue.
Also, if a secondary machine is cycled I find that sometimes I will lose my mouse as I attempt to pass through it to a machine located to its side (move machine by machine away from the primary in a horizontal fashion). This will leave my mouse sometimes unresponsive for a short time after the secondary that had been rebooted is up and function, but sometimes it will leave it unresponsive for several minutes...
Additional info:
My configuration is matched almost identically throughout my team with minor variants in the case of x64.
My setup:
Primary: Winxp64
Secondary1: Winxp
Secondary2: Win2K
Variance setup.
Primary: WinXP
Seconary1: WinXP
Secondary2: Win2K
We are all on a version of Multiplicity Pro that reads 1.6 from within the app and 1.9 on the actual download utility program (using the stardock updater) not sure why these versions do not match)...
Can we get these issues resolved? Is there a setting somewhere I should have opted to enable?
As you probably already know, if someone were to hit cntrl+alt+del to unlock a secondary machine by accident (forgetting the cntrl+alt+bkspc), multiplicty delivers some odd behavior. Sometimes the result is that you cannot click on icons, sometimes alt or cntrl will just not function.... The remedy is to hit all of the previously used keys a couple times on the primary machine and then navigate back to the secondary’s. I have also found that at times the scroll wheel of my mouse will not work until I return to the primary, use it and then swap back to the secondary.
For this to be used in production within our firm, we need this bug worked out. There should be some error checking routines you could include to clear the buffer of stuck keys or input device actions in general. I was told by the sales rep that the bugs I had encountered in the shareware version would not be present in the live, yet I still have this issue.
Also, if a secondary machine is cycled I find that sometimes I will lose my mouse as I attempt to pass through it to a machine located to its side (move machine by machine away from the primary in a horizontal fashion). This will leave my mouse sometimes unresponsive for a short time after the secondary that had been rebooted is up and function, but sometimes it will leave it unresponsive for several minutes...
Additional info:
My configuration is matched almost identically throughout my team with minor variants in the case of x64.
My setup:
Primary: Winxp64
Secondary1: Winxp
Secondary2: Win2K
Variance setup.
Primary: WinXP
Seconary1: WinXP
Secondary2: Win2K
We are all on a version of Multiplicity Pro that reads 1.6 from within the app and 1.9 on the actual download utility program (using the stardock updater) not sure why these versions do not match)...
Can we get these issues resolved? Is there a setting somewhere I should have opted to enable?
WinCustomize Forums