Flagged as virus
Opened this issue · 3 comments
I know it's not infected but Win 11 quarantined it as if it were. Never did that with previous versions and took several days before it did it now.
Also you can find a report on it at virustotal.com.
To my knowledge this false positive issue only appeared after the last update. And since the newer issue is still not resolved I have to assume it is not so simple. It seems obvious that the easiest way to eliminate the new false positive issue is to rollback to the previous version that had the 'working' blue circle problem. Then, if that issue could be corrected in a different way it might manage to avoid using the code that causes the false positive issue. I thought of a workaround that may be worth trying. Based on the fact that the 'working' blue circle disappears when the mouse cursor is placed outside the window for some minimum amount of time (maybe 100-500ms), would it be possible to simply set the cursor to one pixel outside the window for a fraction of a second and then immediately return it to where it was? I know this would be a kludge but it might occur quickly enough to be entirely or nearly unnoticible. If it works and it resolves both issues that would be very satisfactory.
It's really not that easy :(
The problem is not in the last change, but in the compiler and in the update of the antivirus database.
I'm still trying to solve this problem.