I can't test it on my current computer, but does the setting affect menus that are triggered by hovering over something?
If so, then 400ms makes more sense, and the real bug is that menus summoned by an explicit click should be exempt from the delay.
The reason for a hover-delay is that it allows someone to flick their mouse to their real destination without triggering a "trap" of content which pops up on the way to obscure their goals.
epistasis|1 month ago
1. Remove the sleep(30) statement you added a month ago and forgot about"""
-Lars Doucet
neuralRiot|1 month ago
xtracto|1 month ago
I'm so happy I haven't had to use a Windows machine in more than 10 years.
For me, MacBookPro for coding, Linux Mint for home desktop and Steam + Xbox Live online for gaming. We live in excellent times
maccard|1 month ago
Why is this set to 400ms?
Any reason it's not 0?
Terr_|1 month ago
I can't test it on my current computer, but does the setting affect menus that are triggered by hovering over something?
If so, then 400ms makes more sense, and the real bug is that menus summoned by an explicit click should be exempt from the delay.
The reason for a hover-delay is that it allows someone to flick their mouse to their real destination without triggering a "trap" of content which pops up on the way to obscure their goals.
unknown|1 month ago
[deleted]
thesz|1 month ago