No, a simple if statement in the C++ code behind it would only apply the hack if the host system is Windows 10.gallaxhar wrote:#IgnoreWin10Borders, On might conflict with win7 and before compatibility, if it forces winmove to always offset as if the script is running on win 10
Yes it probably shouldn't be, though for a different reason. Because it would allow you to disable the feature temporarily during runtime.so it shouldn't be a directive that executes before runtime probably
You have to understand that changing WinMove in the way you would like it, would introduce new "buggy behavior" and while you personally feel like the new buggy behavior would not be as bad as the old buggy behavior, I beg to differ.