search

RamonUnch / AltSnap

Maintained continuation of Stefan Sundin's AltDrag
GNU General Public License v3.0
2.08k stars 66 forks source link

Intermittently stops interacting with windows #532

Open dsjstc opened 4 months ago

dsjstc commented 4 months ago

After a couple of days of use, AltSnap will stop interacting with windows: my I can no longer resize or drag with a hotkey+drag.

The main process does not crash, and the tray icon remains interactive, but I don't get back window interaction until I exit and restart.

I've attached my .ini, and an ad.log (created with a debug version of 1.63 run through gdb32) that spans an instance of this behaviour. adlog_and_ini.zip

RamonUnch commented 4 months ago

but I don't get back window interaction until I exit and restart.

You need to restart? enabling/disabling is not sufficient?

From the log I do not see anything suspicious. I suspect Win11 does no like a hook to hold for too long and maybe silently disables the whole program from hooking. Also gdb32 generates its own trance, you would need to include the content of the console for extra information, however in this case given there is no crash we do not care about gdb32 results.

dsjstc commented 4 months ago

You need to restart? enabling/disabling is not sufficient?

I have been assuming that left-clicking the tray icon disables/enables. If so, then it is not sufficient.

brentk commented 3 months ago

Not sure if this is the same issue, but I've noticed similar behavior. However, what I've also noticed (in what I'm experiencing) is that it seems to affect exclusively windows that have been snapped.

Whenever the bug presents itself, the vast majority of windows that have been snapped will stop responding alt-drags. For example, if I snap something in the the corner, I can't altdrag unless I first drag it normally by the title bar any distance, then it will start responding again. Dis/re-enabling altsnap by left clicking on it in the task bar will not fix the issue, you need to close it and reopen it. Once you do that it starts behaving correctly again, and I haven't noticed a specific timeframe or action that causes it to stop working again.

PS: I say "vast majority of windows that have been snapped..." since there are odd outliers. Like when I was testing this my VS2022 window would not respond to altdrags when snapped to a corner, but would when snapped to a halfscreen. Outside of this, for the most part it seemed pretty reliable way to trigger the issue. I've since restarted altsnap to confirm that fixes it, so it's a waiting game for it to stop working again.

airtonix commented 1 month ago

Not sure if this is the same issue, but I've noticed similar behavior. However, what I've also noticed (in what I'm experiencing) is that it seems to affect exclusively windows that have been snapped.

This started happening to me too, but only for windows that have been maximised.