Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

When Mouse Filter is set to all, The physical mouse begins acting weird. Possibly because Interceptor thread does not terminate properly. #20

Open
Jamisco opened this issue Jan 27, 2021 · 0 comments

Comments

@Jamisco
Copy link

Jamisco commented Jan 27, 2021

I have a problem where, when I set the mouse filter to All, the mouse begins to act up in really weird ways.

For example, even after I closed my program. It is as though the Interceptor is still intercepting the mouse inputs. When I try to click on a button, the click is not detected by windows, or a control that would be say highlighted if the mouse came over it, would not be highlighted if the mouse came over it.

The only way to bring the mouse back to normal is to completely restart the computer.

I did a little bit of digging and I suspect that one of the reasons why this problem might occur is because the thread become hostile and cannot terminate properly.

If you look at the Unload() method, these lines

            callbackThread.Abort(); // This line is not guaranteed to safely abort the thread
            MouseFilterMode = MouseFilterMode.None;
            KeyboardFilterMode = KeyboardFilterMode.None;

            InterceptionDriver.DestroyContext(context); // I also suspect this does not work as it should
            IsLoaded = false;

If anyone knows the problem Im talking about and how to solve it, please let me know.

Thanks

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

No branches or pull requests

1 participant