Build 8025 (v0.9.1) Release Notes

[djp952]

Build 8025 - v0.9.1 (2021.12.21)

• Initial Public Beta
• Change the IP address label in the device details form to a hyperlink that opens the device web page
• Dynamically generate the tray icon GUID based on a hash of the executable path

Initial Public Beta

Welcome! If you find something broken or think can be made better, please let me know with an Issue.

Change the IP address label in the device to a hyperlink that opens the device web page

This changes the static label in the lower right corner of a device details form that shows the IP address of the device to be a clickable hyperlink that will open the device's web page.

Dynamically generate the tray icon GUID based on a hash of the executable path

Resolves Issue 15 as elegantly as I could come up with. When using a GUID to identify a tray icon, Windows silently ties that GUID to the path of the application that registered it. If the application moves and attempts to use the same GUID, the call to Shell_NotifyIcon (NIM_ADD) will fail and while the application will be running, the tray icon will never appear.

To combat this scenario, the application will now generate an MD5 hash of the executable path and use that to generate the GUID associated with the tray icon. This provides the required uniqueness that Windows needs to allow the icon to appear regardless of where the application was launched from.

This comes with a side-effect, however. Since the GUID changes, Windows will end up with multiple HDHomeRun Status Monitor registrations in the Notification Area Icons (Windows 7), Select which icons appear on the taskbar (Windows 10), or Taskbar corner overflow (Windows 11) settings. The user must also individually choose which registrations to "pin" to the taskbar since they are considered as different applications by Windows.

Users that install the application from the .MSI package are unlikely to ever notice this, as the path will never change, it's more of a concern for users that are building/running the application from source, or for users that would prefer a 64-bit version of the application instead of the 32-bit version (once a 64-bit version is available).

Questions, Concerns? Let me know!