Blur Busters Forums

It's been a while since I posted here! Display Hot Keys has come a long way. I updated the OP. To see changes, visit the "Releases" page on GitHub: https://github.com/jon-mil-92/DisplayHotKeys/releases

A new release is up!

Thank you for continuing to actively maintain this utility!

I admit I haven't tried it recently, but you might have added it already: A hot key that displays the current mode on all displays simultaneously as a temporary overlay popup (monitor number, resolution, refresh rate, bits per pixel, hdr on/off, etc). Make the resolution and refresh rate the biggest text.

Basically like a temporary OSD status message that appears on all displays simultaneously. Whether as big transparent text (like an onscreen menu), or a small dialog at the corner of the monitor.

Sometimes I lose track of which is which, especially when unplugging/plugging a new monitor automatically changes the refresh rate of all displays, as Windows just simply loves to do. Gaming laptop lid opens/close is another wrinkle. The misfortune of everybody who plays with high-Hz multimonitor.

Chief Blur Buster wrote: ↑

21 Aug 2026, 02:06

Thank you for continuing to actively maintain this utility!

I admit I haven't tried it recently, but you might have added it already: A hot key that displays the current mode on all displays simultaneously as a temporary overlay popup (monitor number, resolution, refresh rate, bits per pixel, hdr on/off, etc). Make the resolution and refresh rate the biggest text.

Basically like a temporary OSD status message that appears on all displays simultaneously. Whether as big transparent text (like an onscreen menu), or a small dialog at the corner of the monitor.

Sometimes I lose track of which is which, especially when unplugging/plugging a new monitor automatically changes the refresh rate of all displays, as Windows just simply loves to do. Gaming laptop lid opens/close is another wrinkle. The misfortune of everybody who plays with high-Hz multimonitor.

That's a good idea! I can look into this. I think I'm going to be creating some sort of additional settings menu at some point, and that could be an option in there.

As a Java developer, I am curious to know why this project uses JNI rather than JNA for native API calls ?

Great to see Swing + FlatLAF put to good use in 2026 !

bobbie424242 wrote: ↑

23 Aug 2026, 08:50

As a Java developer, I am curious to know why this project uses JNI rather than JNA for native API calls ?

Great to see Swing + FlatLAF put to good use in 2026 !

Hey thanks! There are actually many reasons I did not, and could not, use JNA for this project. I'll go ahead and list some of them:

• Some of the APIs that I needed to use are not exposed with JNA, such as the DPI scaling API and the DXGI API.

• I have logic for retaining the user's intended display arrangement when changing display settings (Windows does not do this), and this is better suited in native code.

• I have native threads calling back to the Java code, and this works better with JNI.

• I need this implementation to be very performant because it is latency-sensitive, and JNA adds overhead.

On a side-note, Display Hot Keys 4.2.0 (https://github.com/jon-mil-92/DisplayHo ... tag/v4.2.0) was recently released, which includes some performance enhancements and a bug fix! Also, I believe I have finally gotten rid of the antivirus false-positives flagged by VirusTotal: https://www.virustotal.com/gui/file/7ab ... 3a485b2c1d

Thank you for the elaborate explanation.

On the all-displays mode overlay — one thing worth getting right if you build it: EnumDisplaySettings hands you dmDisplayFrequency as a DWORD, so it arrives already rounded to an integer. 59.94 comes back as 59 or 60 depending on the driver, never as 59.94, and 119.88 lands on 119 or 120. Those NTSC-fractional modes are exactly the ones people lose track of, so an OSD built on DEVMODE would stay quiet about the case it is most wanted for.

QueryDisplayConfig avoids that. DISPLAYCONFIG_PATH_TARGET_INFO.refreshRate is a DISPLAYCONFIG_RATIONAL, so 60000/1001 and 60/1 stay distinct instead of both collapsing to 60. Cheap to render as either the exact fraction or a two-decimal figure, and it is already per-target, which fits the all-monitors-at-once layout being asked for.

One caveat for the UI wording: that is still the nominal mode, not measured output. The panel's real rate drifts off the mode's rational, which is the reason Blur Busters' own RefreshRateCalculator estimates Hz from VSYNC timestamps rather than asking the OS. For a "which monitor am I looking at" overlay the nominal rational is the right call — just worth not letting it read as a measurement.