Cursor Jumps to Master When Scrolling On Slave
61 views
Skip to first unread message
Daniel Wojcik
Nov 2, 2016, 12:35:53 AM11/2/16
to Input Director
Both systems: Windows 10, x64, v10.0.14393, Master is Enterprise, Slave is Pro
Master: dual monitors
Slave: single monitor
Mouse: Evoluent 4 driver v5.61 (but the same happens with the generic MS mouse driver)
Input Director: whatever the latest is. :p
Now that that's out of the way:
When I scroll on the Slave, the cursor jumps to the extreme lower left of the Master's main monitor.
Unless I scroll very very slowly, like one tick at a time.
Any idea what could causing that?
an0n1m0us
Feb 27, 2017, 5:20:22 PM2/27/17
to Input Director
Experiencing very similar problem myself.
Otherwise absolutely adore this program. It's incredible.
Master: Windows 10 Enterprise 2015 LTSB (10.0.10240 Build 10240)
Slave: Windows 8.1 Pro (6.3.9600 Build 9600)
Master: dual monitors (external screens)
Slave: single monitor (laptop screen)
Mouse: Evoluent VerticalMouse 4 (Driver: c:\windows\system32\drivers\hidusb.sys (10.0.10240.16384, 37.50 KB (38,400 bytes), 10/07/2015 8:59 PM)
When I scoll on the slave system, fairly quickly but not immediately, the cursor moves to the bottom right of the slave desktop, give or take a few pixels and then very quickly to the bottom right of first of the dual monitors.
msinfo32 Components > Input > Pointing Device details on the Master setup: http://i.imgur.com/spcwQxb.png
I dont exactly have a different mouse to try but I can try to arrange one if it would help.
Otherwise absolutely adore this program. It's incredible.
Master: Windows 10 Enterprise 2015 LTSB (10.0.10240 Build 10240)
Slave: Windows 8.1 Pro (6.3.9600 Build 9600)
Master: dual monitors (external screens)
Slave: single monitor (laptop screen)
Mouse: Evoluent VerticalMouse 4 (Driver: c:\windows\system32\drivers\hidusb.sys (10.0.10240.16384, 37.50 KB (38,400 bytes), 10/07/2015 8:59 PM)
When I scoll on the slave system, fairly quickly but not immediately, the cursor moves to the bottom right of the slave desktop, give or take a few pixels and then very quickly to the bottom right of first of the dual monitors.
msinfo32 Components > Input > Pointing Device details on the Master setup: http://i.imgur.com/spcwQxb.png
I dont exactly have a different mouse to try but I can try to arrange one if it would help.
an0n1m0us
Feb 27, 2017, 5:20:22 PM2/27/17
to Input Director
I might have found a solution to this problem.
Prior to finding and trying Input Director, I was toying with Winaero Tweaker. Amongst many options, it enables the age-old Xmouse option where WIndows activates the window your mouse is hovered over without having to click. I've toyed with it often but never stuck with it. Anyway there's also an option to hange scrolling behaviour in the same spot. I set this back to "Scroll only active window" on both master and slave systems and all of sudden both systems, along with the Input Director integration, is now behaving as expected, even when scrolling!
Here's the program screen in question:
http://i.imgur.com/tzw1tbe.png
It's a free program so should be a low-barrier fix hopefully :)
The only other change I can remember making is removing ASUS Smart Gesture from the slave laptop.
Best of luck!
Prior to finding and trying Input Director, I was toying with Winaero Tweaker. Amongst many options, it enables the age-old Xmouse option where WIndows activates the window your mouse is hovered over without having to click. I've toyed with it often but never stuck with it. Anyway there's also an option to hange scrolling behaviour in the same spot. I set this back to "Scroll only active window" on both master and slave systems and all of sudden both systems, along with the Input Director integration, is now behaving as expected, even when scrolling!
Here's the program screen in question:
http://i.imgur.com/tzw1tbe.png
It's a free program so should be a low-barrier fix hopefully :)
The only other change I can remember making is removing ASUS Smart Gesture from the slave laptop.
Best of luck!
On Wednesday, November 2, 2016 at 3:35:53 PM UTC+11, Daniel Wojcik wrote:
Reply all
Reply to author
Forward
0 new messages