Comment 5 for bug 190208

@Matthias

ok, I suppose now that your problem is the daemon:

Maybe that I should have clarified in the Main Inclusion Report that the daemon only runs when the user activates one of the features it implements. In other words, when the user activates for example dwelling in the Mouse control panel, the mousetweaks process gets started. And deactivating the dwelling feature kills the process. (The same also happens with the Simulated Secondary Click.)

So there is no additional process running on the machine if the user does not use the features it implements.

To be complete, there is a way to start mousetweaks at the command line without activating any feature; but even if the user would not kill the mousetweaks process before logout, it would not automatically restart at the next login. But what sense would it make to start mousetweaks by command line without activating one of its features? Finally, this situation is not possible when mousetweaks is controlled by the corresponding gui (the Accessibility tab of the Mouse control panel).