[Bug] Incorrect behavior of double click

[Tearth]

When clicking rapidly between commits or changed files, Fork interprets this as a double click even when there was only one click on an item - this leads to annoying situations like accidental staging/unstaging of files, or displaying checkout commit prompts when something was clicked too fast.

[DanPristupov]

Wow, you are fast.

We'll try to reproduce that. Looks like two separate clicks are considered as a double click.

Can you reproduce that in the commit list?

[Tearth]

Sure, here is a similar situation in the commit list. Thanks for the fast response, I really appreciate that.

[DanPristupov]

Thank you!

Could you check if the problem exists in the list view in the file history window? I'd expect fast clicks to work properly there.

If it's so, we'll fix that bug in the next update (1.76).

[Tearth]

I think it's present there too, as shown on the gif below, it switches to the "Add Zobrist hash" commit just after one click.

[DanPristupov]

I definitely cannot reproduce that and I believe I made clicks faster than on the video.

1. Do you use any special mouse or mouse tweaking software?
2. Can you reproduce the problem in other applications? In Windows Explorer or Visual Studio, for example?

[Tearth]

1. I use Logitech G HUB to support my Logitech G502 mouse, but if I recall correctly, the issue appeared instantly after the last Fork update. I've tried to close this app, but nothing changed.
2. Unfortunately I couldn't reproduce it anywhere else, this behavior is only present in Fork.

So summarizing, I guess we can't do much more if you can't reproduce it - I will try to investigate it further, so if I find something, I will let you know in this issue. Thanks for the support!

[Tearth]

Well, I had a BSOD yesterday and it forced me to restart the computer (I usually do it very rare) - it turns out that it actually resolved the issue, so while I still don't understand where exactly was the problem, it had to be related to some other app or OS itself.