VMware Communities
JaimieV
Contributor
Contributor
Jump to solution

Slow mousewheel turns ignored in Unity mode (3.0)

I've checked that I'm on the latest drivers, uninstalling and reinstalling the VMware Tools, but Unity

mode persists in ignoring single mousewheel turn clicks (Logitech MX1000 and Logitech

Revolution in clicky mode). Client application windows - Windows

Explorer, for example - only respond to mousewheel turns over a certain

velocity, it seems - single clicks do nothing, slow roll does nothing,

a faster roll and suddenly it's working. Maybe around 10Hz is the minimum required.

On reverting to single window mode, the mousewheel behaves perfectly -

one click = application scrolls by the defined number of lines.Two

clicks, two times as far. Roll the wheel, get lots of scrolling.

Reverting to 2.0.6 also works perfectly.

This is on OSX 10.6.1, Mac Mini (early 2009), Logitech Control Panel 3.10

(latest) and also 2.6 (previous). Client is XPsp3 patched up to date, VMware

tools installed.

This issue basically kills Unity mode for me. I've been using Single Window since identifying that scrolling works fine there.

0 Kudos
1 Solution

Accepted Solutions
admin
Immortal
Immortal
Jump to solution

Sorry for the inconvenience, and thanks for reporting the bug - I've seen it too, but didn't get around to filing it until your post. This is our bug (unrelated to third-party drivers) and has been fixed internally.

View solution in original post

0 Kudos
6 Replies
doghausdev
Contributor
Contributor
Jump to solution

I am seeing this too.

0 Kudos
JaimieV
Contributor
Contributor
Jump to solution

Is that with the Logitech Control Centre, or otherwise? I'm wondering if I should try ditching it.

0 Kudos
JohnSan
Contributor
Contributor
Jump to solution

I have the same issue. Using microsoft wireless mouse and no Logitech Control Center. Just the default Windows XP mouse driver.

0 Kudos
numist
Contributor
Contributor
Jump to solution

thanks for reporting this, I've filed a bug and hopefully we can get it sorted out in a point-release.

0 Kudos
admin
Immortal
Immortal
Jump to solution

Sorry for the inconvenience, and thanks for reporting the bug - I've seen it too, but didn't get around to filing it until your post. This is our bug (unrelated to third-party drivers) and has been fixed internally.

0 Kudos
JaimieV
Contributor
Contributor
Jump to solution

Thanks very much! Looking forward to that point release.

0 Kudos