-
Notifications
You must be signed in to change notification settings - Fork 31
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
Used to be able to set very high cps (Clicks per second) #5
Comments
Hi wolfy01! What version was the fastest? I have some ideas how to
fix that...
…On Sun, Jul 19, 2020 at 4:59 PM wolfy01 ***@***.***> wrote:
When I last used The Fastest Mouse Clicker for Windows, it truly was the
fastest, I was able to set high cps like 500 and it would work fine. Now,
after downloading and using this one, I can no longer do that. Setting a
high cps like 500 seems to actually only be 100 cps instead of the 500 I
set.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#5>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACMGUBRUGZEFNM5DHA4LO4LR4NNB3ANCNFSM4PBSKGEA>
.
|
Fixed in v2.5.4.0 - Aug 01 2020. |
Sorry for the late reply. Also the latest release did fix the issue |
Great!
…On Wed, Aug 26, 2020 at 10:11 PM wolfy01 ***@***.***> wrote:
Sorry for the late reply. Also the latest release did fix the issue
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#5 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACMGUBT3VBUR6ZO55M2IVQLSCW6F3ANCNFSM4PBSKGEA>
.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When I last used The Fastest Mouse Clicker for Windows, it truly was the fastest, I was able to set high cps like 500 and it would work fine. Now, after downloading and using this one, I can no longer do that. Setting a high cps like 500 seems to actually only be 100 cps instead of the 500 I set.
The text was updated successfully, but these errors were encountered: