RamonUnch

I see on the video, but still cannot reproduce the bug with your .ini file (not using Win 10 however). Does setting a primary action fixes it? In this case,...

Just in case tell me if this one fixes it (I do not know if it will): [AltSnap-1.53test24_i386.zip](https://github.com/RamonUnch/AltSnap/files/8843411/AltSnap-1.53test24_i386.zip) [AltSnap-1.53test24_x64.zip](https://github.com/RamonUnch/AltSnap/files/8843413/AltSnap-1.53test24_x64.zip) This build also include other non-related features and fixes.

Well I could finally get access to a Win10 computer, reproduce your bug and, fix it: [AltSnap1.53-test26_i386.zip](https://github.com/RamonUnch/AltSnap/files/8957825/AltSnap1.53-test26_i386.zip) [AltSnap1.53-test26_x64.zip](https://github.com/RamonUnch/AltSnap/files/8957826/AltSnap1.53-test26_x64.zip) It works for me on Win10 using your .ini file.

This is duplicate of #106 If you want to see a preview of snapped windows, I suggest you set `FullWin=0` in the `[Performance]` section of the ini file. It will...

Yes indeed, sorry for that but the choco package no longer passes the automated validation and I do not understand the error, I have no time to investigate deeply so...

here is the compiled nupkg file that I uploaded. [altsnap.1.63.nupkg.txt](https://github.com/RamonUnch/AltSnap/files/15441745/altsnap.1.63.nupkg.txt) (this is actually also a zip file you can you can open with 7-zip or similar software). my protocol is...

> I assume the .txt extension was just for inserting it on github?! I've managed to upgrade to 1.63 just fine with that nupkg (after removing the .txt extension). Indeed...

Also when the package is just uploaded to choco and not yet validated you can still force the update with the --version parameter. Wwhen I did that it was working...

I will try again with 1.64 when it will be ready (hopefully soon).

Seems like a joke, just the version number scheme did not please them? they could issue a warning in the validation process. I was using indeed choco-1.20 I never updated...