Seems like there's a bit of a conflict with this PR since I merged the others.

That said, I'm not sure this is the approach we want to go down. On macOS and Linux we get a simple counter of how many clicks a user has made, which can go as high as the user wants. Is there a compelling reason to use the NCBUTTONDBLCLICK mechanism, over an approach like in this PR: #9608, except using GetDoubleClickTime() instead of hard coding it?

Seems like there's a bit of a conflict with this PR since I merged the others.

That said, I'm not sure this is the approach we want to go down. On macOS and Linux we get a simple counter of how many clicks a user has made, which can go as high as the user wants. Is there a compelling reason to use the NCBUTTONDBLCLICK mechanism, over an approach like in this PR: #9608, except using GetDoubleClickTime() instead of hard coding it?

Oh, I didn't notice these double click changes in other playforms. If you wish, I can implement it for the Windows platform in a way similar to how other platforms handle the double-click mouse event.

I think it would be best to match the other platforms and do things simply, unless there's a good reason to use the NCBUTTONDBLCLICK approach, in which case we should augment it with the behavior of the other platforms :)

Cargo clippy complains "recursion limit reached while expanding #[test]", should I move the tests to another file?

"recursion limit reached while expanding #[test]"

That is caused by doing use crate::*;, which currently doesn't work inside GPUI.

"recursion limit reached while expanding #[test]"

That is caused by doing use crate::*;, which currently doesn't work inside GPUI.

I have changed that, thanks!

Thank you!