Curosr and window getting glued together

[RamonUnch]

what about 1.66?

not work either, and there is a huge bug in 1.66 and 1.67, that's why I keep using 1.65.
(sorry I can't figure out how to trigger this bug for now)
As you can see, curosr and window are glued together, I can't click anything (so I had to record it with phone):

youtube recording video link

Originally posted by @Mj65536 in #696

[RamonUnch]

@Mj65536

When you find a way to reproduce report more details. Also giving your ini file can help.
Does pressing ESC fix the problem when it happens?

[Mj65536]

@Mj65536

When you find a way to reproduce report more details. Also giving your ini file can help. Does pressing ESC fix the problem when it happens?

I will try to reproduce this bug, only apply Alt + F4 to window can stop bug, and this is my ini file for 1.65 and 1.67test13:

AltSnap1.65ini.txt

AltSnap1.67ini.txt

and their difference below:

(note: I changed both RezTimer & MoveRate from default 2 to 3, 165Hz monitor and 1000Hz polling rate Logitech G502 mouse)

[RamonUnch]

maybe the EndSendKey is the reason (try EndSendKey=11 instead of FF) but I will check the diff in the AltSnap source...

[RamonUnch]

Also given the relative mouse frequency to the monitor refresh rate you could try to bump up MoveRate=4, not sure if you would notice the difference.

An interesting test would be to see if when setting MoveRate=1 the Issue is more common..

[RamonUnch]

The only other thing I found that could have an effect is the check that was added for UWP contained in an ApplicationFrameHost.exe process. #645, 646

Here is a version without this check:
AltSnap1.67test14_no_ApplicationFrameHost_check.zip

[RamonUnch]

Did anything above made any difference?

[Mj65536]

Did anything above made any difference?

I simply set EndSendKey=11 and MoveRate=4 as you suggested, and not meet the bug again during the past 3 days, can't provide more info for now, maybe you could release v1.67 stable and check if someone meet similar bugs ?

[RamonUnch]

Thanks, very interesting, maybe I should set EndSendKey=11 by default again but I put EndSendKey=FF to avoid some problems other users FF. The EndSendKey is used .

Anyway I will release 1.67 hopefully soon, It will be mainly bug fixes compared to 1.66 so any time would be a good time.
I tried to reproduce your Issue but I could not. We have different settings though (I have 60Hz monitor and a typical 125Hz mouse).

Having new features is nice but having AltSnap as stable and bug-free as possible is more important because any bug slows down day-to-day workflows.

I will keep this issue opened so people can find they are not alone if they have the Issue.

[Mj65536]

Thanks, very interesting, maybe I should set EndSendKey=11 by default again but I put EndSendKey=FF to avoid some problems other users FF. The EndSendKey is used .

Anyway I will release 1.67 hopefully soon, It will be mainly bug fixes compared to 1.66 so any time would be a good time. I tried to reproduce your Issue but I could not. We have different settings though (I have 60Hz monitor and a typical 125Hz mouse).

Having new features is nice but having AltSnap as stable and bug-free as possible is more important because any bug slows down day-to-day workflows.

I will keep this issue opened so people can find they are not alone if they have the Issue.

excellent software and developer, thank you !