Closed GoogleCodeExporter closed 9 years ago
[deleted comment]
Any suggestions for how to provide info which would help identify the problem?
Original comment by bob.kitz...@gmail.com
on 7 Oct 2010 at 2:36
There are a few things you should check to narrow down the problem.
Do you see high CPU when the mouse movement becomes jerky?
Does the problem disappear when you remove the pager from the taskbar?
Also, can you install the previous version
http://code.google.com/p/vwkvasdopager/downloads/detail?name=vwKvasdoPager-0.4.3
a.zip&can=1&q= and see if the problem persists?
Thanks
Original comment by alexandre.jasmin
on 7 Oct 2010 at 4:31
At the time my CPU was not spiking, and the problem went away when I removed
the pager, came back when I added the pager, etc.
However, I just now re-enabled the module and added the pager, and the jerky
movements do NOT appear. I hate it when that happens :-)
Original comment by bob.kitz...@gmail.com
on 7 Oct 2010 at 5:59
The problem has resurfaced, and it depends on CPU activity. It my CPU is
active (say, loading an app) then the mouse gets all jerky. This doesn't
require much of a CPU load to impact the mouse movement (i.e. just normal
knowledge-worker type activity). Closing the pager toolbar gets the mouse back
to normal.
Original comment by bob.kitz...@gmail.com
on 8 Oct 2010 at 12:17
After further use I have to concur with Bob, vwKvasdoPager does cause jerky
mouse cursor movement when the computer is under moderate to high load.
Disabling vwKvasdoPager while the issue is occurring eliminates the issue.
Original comment by jmtyso...@gmail.com
on 3 Nov 2010 at 1:53
Can you install the previous version and see if that helps. See comment #3.
Original comment by alexandre.jasmin
on 3 Nov 2010 at 4:54
I restarted with the previous version (0.4.3a) loaded and did *not* experience
the stuttering, jerky mouse movement as I did with v0.5.1a.
Original comment by jmtyso...@gmail.com
on 5 Nov 2010 at 7:57
I found a way to reproduce this reliably on my machine.
I experienced this before but thought it was just a random mouse tracking
problem. Thanks bob.kitzberger and jmtysonjr for filling this bug.
Here's a patch that appears to fix the problem. The mouse wheel support added
in 0.5a was in cause. Attached patch move the mouse hook in it's own thread to
prevent it from blocking mouse input.
Please try the attached build and tell us if it helps.
Original comment by alexandre.jasmin
on 8 Nov 2010 at 9:08
Attachments:
Great thanks to alexandre, i'll commit the patch and update the binaries as
soon as possible.
Original comment by kvasdo...@gmail.com
on 8 Nov 2010 at 9:25
Actually could you use this patch instead?
Runs the thread at an higher priority level.
Original comment by alexandre.jasmin
on 8 Nov 2010 at 12:42
Attachments:
Alexandre, I tried your fix and it appears to work!
Previously, I experienced the jerky mouse pointer problem during the startup of
Windows when all of the services and tool-tray stuff is coming up. I attributed
it to loading too many programs, PGP whole disk encryption and not enough
memory (2GB). When I upgraded the memory and still experienced the problem
during startup I disabled the pager and the problem went away.
Original comment by jmtyso...@gmail.com
on 8 Nov 2010 at 2:17
[deleted comment]
Shutdown VirtuaWin and overwrite the existing vwKvasdoPager.exe with the
contents of vwkvasdopager-issue34-build-1.zip from comment #9 above. Restart
VirtuaWin, done.
Original comment by jmtyso...@gmail.com
on 10 Nov 2010 at 4:50
jmtysonjr, here's a build with the second patch applied.
If you just want to try the fix then exit VirtuaWin and replace your copy of
"C:\Program Files\VirtuaWin\modules\vwKvasdoPager.exe" by the one in the zip.
Only that file has changed.
If you mean applying the diff to the source code you have a couple of options.
Such as using the "patch" utility or the "Apply patch" feature of Tortoise SVN.
Original comment by alexandre.jasmin
on 10 Nov 2010 at 4:56
Attachments:
err, I mean pdxbob456 here's a build...
Original comment by alexandre.jasmin
on 10 Nov 2010 at 4:58
Original issue reported on code.google.com by
bob.kitz...@gmail.com
on 6 Oct 2010 at 8:32