Zardoz2293
36 discussion posts
Windows 10 Pro OS: 1703, Build 15063.413, 64-Bit on a Dell Precision 7720
TrayStatus = v3.1 (Trial)
The following (Caps, Num, ALT, CTRL, SHIFT, WIN only ones tested) have a SIGNIFICANT delay (guess 50-150ms or longer) in toggle/status change-- so long that quick toggle will never get indicated. Sometimes the response is very good, clicking multiple times in a row, at the same speed, most will not be detected.
Installed significant software:
* DisplayFusion v9.0 (Beta 3)
* VMware Workstation Pro v12.5.6 build-5528349
* ESET Smart Security v10.1.210.0
* TrueLaunchBar v7.3.5 RC1 (64-bit)
* Process Hacker v2.39.124
* JetBrains Toolbox v1.3.2421
* Epson Status Monitor 3 v8.0.1.2
* Epson Event Manager v3.2.0.0
* Samsung Magician v5.0.0
* Dell Touchpad v10.2207.101.108
* MouseKeys (OS)
That's pretty much expected, as we poll for the key status every 100ms or so. We poll instead of hooking the keyboard because we just wanted to avoid hooking the keyboard. We'll look into polling more frequently, but it will depend on how much that ends up using the CPU.
Zardoz2293
36 discussion posts
1. Requesting consideration to allowing end-user configuration to polling frequency.
2. Why not a simple (low overhead) hooking of the keyboard handler? Seems like it would have lower overhead than having a higher frequency of polling and, yet, would be highly responsive. I've written code like that and was able to get extremely efficient results and no negative results.
We would add an advanced setting to set the polling interval for sure. If it's not too much work, we may also try out keyboard hooks to see if they'll work better and still be reliable.
Thanks!
Zardoz2293
36 discussion posts
I worked on some keyboard hooking once and achieved significant performance enhancement myself. I'm open to assisting, on this or any of the other suggestions on DisplayFusion. My offer is driven by the fact I like the product(s) and I'd do things that would enhance my personal workflow (and others as well). Private email.
