Mouse Cursor Very Laggy on Windows Startup/Invisible cursor about altsnap HOT 12 CLOSED

Maybe upgrade to the later v1.34...
And tell me if it happens again in the future.

from altsnap.

By reviewing old issues on the original AltDrag, I found this one: stefansundin/altdrag#77
The trick is to add a delay so that AltDrag is not lunched immediately at logon.

from altsnap.

I haven't noticed the bug since setting UseCursor=0. I will set it to 1 now and see if I encounter it again (using v1.38).

from altsnap.

After thinking a little more I think this may have beed due to the infinite loop that may occure in the Tray icon handeling. this was fixed with 1.33. This was an AltDrag.exe bug so it makes sense that you encountered using v1.32.
Has any one encountered this problem again?

from altsnap.

I've delayed the process on start-up, but I did notice something else which I never had before: my cursor was invisible and I believe it had to do with AltDrag. Haven't seen it since (I don't reboot regularly).

from altsnap.

The only way AltDrag could interact with mouse cursor is through a small invisible window that will diseappear on ESC, or on a click,
AltDrag does not change the system cursors,it just creates this small invisible window that tell which cursor should be shown when the mouse pointer is in on its top.
I had invisible cursors on boot with Win10 regularry without altdrag in autostart because of buggy mouse and/or bad usb connection.

from altsnap.

I just woke my PC from hibernation and experienced an invisible mouse cursor again.

I managed to close AltDrag via the system tray icon, and when launching the executable again, the cursor returned.

I'm fairly positive it's related to AltDrag in some way.

from altsnap.

The cursor returned when lunching AltDrag not quitting?
You closed AltDrag via the tray, so you could still click, the cursor was just invisible?
Could you try with UseCursor=0 in the [Advanced] section of AltDrag.ini

Could you find a sequence to reproduce, because I tried to sleep awake on three different computers (Win10 20H2, Win10 2004, and Win8.1) more that twenty times on each without experiencing this issue.

from altsnap.

The cursor returned when I launched AltDrag, yes. Not when quitting. But it could be there was some kind of delay. I will have to pay more attention. The icons in the tray highlight when you go over them so I was able to right-click AltDrag this way.

I am a bit busy unfortunately, but I'll try keep a track if it happens now that UseCursor=0.

from altsnap.

I Slightly changed the way the cursor is handled, it should be even less intrusive.
It will be in the next release, hopefully for this week-end, it will have quite some changes...

Did you experience more cursor problems with UseCursor option set to zero?

from altsnap.

I haven't, though I don't think the testing is conclusive yet as it may have been caused by another program on my system.

The AltDrag ini option is still set to 0 and now the other program is set back to its original setting. This way I will know if it is the other program or the ini setting. If you ask me in another week, I can probably tell you a more accurate answer.

from altsnap.

I will consider it closed (open a new one if you get again similar problems).

from altsnap.