PDA

View Full Version : Mouse tracking problems?


liquidmillennium
31st May 2000, 06:04
I have used Winamp on a few different machines, including a Win '95 machine, and a few running Windows '98, but I have not previously run into this problem. The Mouse (logitech brand) jumps whenever it crosses into a 'hot spot'. For example, I try to click on stop, and before entering the 'hot spot' that is the area for the stop button, the pointer jumps across the area, and stops just outside of the opposite side of the 'hot spot' Usually I am pretty good at tracing down problems, being that they are most often with the users set up, but this one I'm not sure about. Any Ideas? Solutions?

gandalf
31st May 2000, 10:18
Try closing (not minimizing) winamp and starting it again.

Raptor of Axys
1st June 2000, 08:18
I've encountered this problem also. It seems to occur only when using custom cursors though... and I'm using a microsoft mouse.

Graoul
7th June 2000, 19:28
I have this problem, with WinAMP running on my WIN98 platform. I have a genuine Microsoft Wheel Mouse, and it happens when using all skins and cursors. Gandalf recommended turning WinAMP off then reopening, this works as I already knew, but will this bug be fixed in the future - I have noticed it ever since early versions of WinAMP 2.x

highlandr
10th June 2000, 23:23
I have the same problem, and I've found it usually occurs after I've been playing a fullscreen game, ie Halflife, quake2, etc... closing and restarting winamp works as a temp. fix...

Z-Man
23rd June 2000, 19:28
I have the same problem, they seemed to of fixed it awhile back, but it reared its ugly head again. For me, it now happends when you run a copy of PC Anywhere. After you leave the session (Im conducting a remote session with my downstairs computer) and return to a previously open winamp (Open BEFORE you started the remote session) the mousing is all out of sync, encompassing the major tracking issues. I have a strong feelings its due to the custom cursors and "hotspots" winamp ueses.

Matt Zayatz
z-man@optonline.net

old and quite mad
23rd June 2000, 19:37
I've run into this a couple of times. Gandalf's suggestion usually works. It seems like one time I had to reboot? (long time ago...me no remember too good)

Seems like one or two skins were more prone to doing this than others??



[This message has been edited by old and quite mad (edited June 23, 2000).]