Windows mouse cursor wrong after clicking on fence

from WinCustomize Forums

I am not sure if this is an isolated problem but if I do the following:

Open a folder window containing some file

Click any of the fence I have setup

Click back to the explorer window

I am intermittantly left with the incorrect mouse cursor, instead of the default pointer I get either a four way drag cursor or a vertical bar cursor.  I have to click on the windows desktop or another application (outside of fences) and then back to the folder window to get the cursor back to the pointer.

This is intermittant but I have been unable to reproduce it from clicking on any other applications, it is only after clicking on a fence that it occurs.

Whilst not a big problem I thought I would mention it incase anyone else has experienced it.

fences
16,658 views 7 replies +1 Loading…
Reply #1 from WinCustomize Forums Top

Doesn't happen here...on 4 separate installs of Fences.... win 7 Ult 64 [2]....win XP Pro and Vista Ultimate 32.

Post your OS info at least...)

Sins of a Solar Empire II
Reply #3 from WinCustomize Forums Top

I am having the same problem with XP sp3.

I didn't realise it was due to Fences until I read this post. So thank for that - I though I was the only onr on the net who was experiencing it.

 

At least I know wha tis causing it now.

Reply #4 from WinCustomize Forums Top

Actually, the problem is a little more subtle than originally described.  It has nothing to do with clicking and everything to do with mouse position.  If the mouse cursor is over the title area of a fence ('four way' drag cursor) or one of the edges/corners (i.e. any of the resizing mouse cursors - vertical, horizontal or angled) and moves directly from that position to any window without first going over the desktop, then the mouse cursor will be 'stuck' when it is over the file list portion of any Windows Explorer window.

The key (to reproducing the problem consistently) is to avoid moving over the desktop, which will 'reset' the mouse cursor to an arrow, before moving to another window (Windows Explorer or otherwise).  The cursor will remain 'broken' for Windows Explorer, from that point forward, as long as you avoid going over the desktop (including the space inside your fences).

I would be curious if someone could try this again on Windows 7, with the new information, to see if it is truly unique to Windows XP (running XP Pro, myself).

- Grant

Reply #5 from WinCustomize Forums Top

Same problem here under XP Pro SP3 X86, but no problem under Win7 Ultimate X86 (perhaps because Win7 has a larger window border, and when your mouse passes over that border, its pointer is also reset, exactly as if you moved over the desktop background).

The bug has been perfectly described by GTregay in the previous post.  IMO, although the bug is minor and doesn't cause crashes or data loss, it should be fixed, as currently the wrong cursor is very confusing and unpleasant.

Note that one way to avoid that bug is simply to Lock Fences.  When the fences are locked, you cannot move or resize them, and the cursor is always the standard arrow.

 

Reply #6 from WinCustomize Forums Top

I am having the same problem on xp pro. In addition to the cursor issue my cursor speed slows down until i click on another opened window. If I change mouse acceleration to "none" my problem goes away.

 

Basically when I click on any icon inside a fence or on the fence itself, my mouse accelerator vanishes as if I have it set to "No Acceleration". My work around up to this point is to manually turn off the accelerator and just increase my mouse speed overall until there is hopefully a fix out.

 

 

Reply #7 from WinCustomize Forums Top

I am having the same problem.

I found a video on YouTube showing the exact problem:  http://www.youtube.com/watch?v=Zd0zQRGN6gg

My system details:

Fences (Free Version) v1.00.27.87

Win XP Media Center Edition, SP3

Dell Inspiron Laptop e1505

Video chipset:  Mobile Intel 945G Express Chipset w/ generic driver

Are there plans to fix?

I love this program.