Skip to content

Conversation

iG8R
Copy link
Contributor

@iG8R iG8R commented Oct 5, 2025

Hello.
Well, the title speaks for itself.
I think this solves the issue with denied access to the path where WinSize4 saves its configuration files.
PS. Sorry for the mess with the number of commits, I'm still getting used to GitHub from VS2022.

@tomasrudh
Copy link
Owner

tomasrudh commented Oct 10, 2025

Not sure what the idea is with that last commit, wouldn't that invalidate the setting for Always Move? Commit 4925832

@iG8R
Copy link
Contributor Author

iG8R commented Oct 10, 2025

The thing is, when the saved position and size are identical to the current ones, there's no need to process this window, even if the AlwaysMove flag is set, because... the positions and sizes are identical.
Without such a fix, I don't know about your experience, but in my case, some windows processed by WinSize4 flicker even with the same parameters.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants