v2.3.9437

Once again, much more time has passed than I had expected to put out a small pre-release like this. I know some of you have been eagerly awaiting this so I apologize for the delay. I had ambitions to complete the ClickOnce migration, but that will have to wait for a future pre-release. For now, please find the immediate changes below:

What's Changed

• ClickOnce Build Workflow in #180
• Fix Connected toast, logged in state in #183
• Fix FR Language by @Vincent55200 in #196
• [BUGFIX] 195: Ensure battery runtime (when unavailable) will not be used as shutdown trigger by @SebastianOehm in #217
• Updated WinNUT-client.de-DE.xlf by @codiflow in #200
• Enhanced GetUPSVar to support variable name arrays by @leongurman in #215
• Correct broken reference in Setup project in #219

New Contributors

• @Vincent55200 made their first contribution in #196
• @SebastianOehm made their first contribution in #217
• @codiflow made their first contribution in #200
• @leongurman made their first contribution in #215

Full Changelog: v2.3.8988...v2.3.9437

v2.3.8988

What's Changed

• Update Overhaul Part 1 - Octokit Library in #176
  • WinNUT updater code overhauled in anticipation of further changes in WinNUT. The Updater GUI looks and functions the same for the most part. In need of translations (although you may want to wait for the next part of this update before making translations.)
  • Added a third party library (Octokit) in favor of custom update query code.
  • Removed the Auto update option since WinNUT doesn't have the functionality to check for an update periodically during operation, it can only check at startup under a different option. See #175 for more info.
  • Please keep in mind that the impacts of these changes won't be completely in force until the following update. I've tested this a few times on my own computer, but the ultimate test won't be until later.

Build automation

• Modify MSBuild command, version upgrades in #178

Full Changelog: v2.3.8981...v2.3.8988

v2.3.8981

What's Changed

• Persistent Connection attempts, quieter notifications in #171
  • Slightly changes the Connection menu in WinNUT. Added some icons, as well as a toggle for keeping a persistent connection (reflects with the Auto Reconnect option in the Preferences menu)
    
  • WinNUT now attempts to keep a connection indefinitely. There should be less notification spam as well.

Full Changelog: v2.3.8970...v2.3.8981

v2.3.8970

Sorry about the broken installer if you were able to download it in the last pre-release. That led me to deploy an update in AGauge which not only fixed that, but another older bug as well. I guess I can't blame this one on CrowdStrike. 😅

What's Changed

• Separate AGauge into a NuGet package, with inherited control in #59
• locale: add Ukrainian language by @Vladdrako in #160
• More efficient connection handling, better suspend/resume support in #163
  • Better tolerance of NUT servers behaving strangely (s/o to Synology)
  • Login command now works correctly, and is not critical for connecting to your UPS. Try deleting your username and password and see if everything still works.
  • Official support for network protocol version 1.3
  • Polling interval is no longer ignored (always defaulted to 3.0 seconds)
• Revert Polling Interval display to seconds in #164
• AGauge - fix tick mark bug in #168
  • Also fixes the broken installer in #167.

Hotfix: The Ukrainian translation was not building - that has been corrected (and MSI/zip have been updated too.)

New Contributors

• @Vladdrako made their first contribution in #160

Full Changelog: v2.3.8892...v2.3.8970

Pre-Release v2.3.8892

What's Changed

• Power value calculation updates (specifically for Huawei UPS) by @gbakeman in #151
• Update zh-cn language and add UPS States flag by @MaxMadcc in #152

Full Changelog: v2.3.8883...v2.3.8892

Pre-Release v2.3.8883

What's Changed

• Fix 'Create LogFile' option is on, but the option is not working when program is running. by @MaxMadcc in #147

Full Changelog: v2.2.8834...v2.3.8883

Pre-Release v2.3.8834

What's Changed

• Fixed the bug where the UPS using battery power was not displayed. by @MaxMadcc in #137
• ⚠️ Fix Application Settings not carrying over on upgrade/update in #140

New Contributors

• @MaxMadcc made their first contribution in #137

Full Changelog: v2.3.8824...v2.3.8834

Pre-Release v2.3.8824

What's Changed

Several bugfixes for when the NUT server is reporting unexpected, out-of-range values (see also #131). In addition;

• Fixed an issue where log file controls were enabled when logging was not enabled, and the log file was not present
• Fixed being unable to change update interval value, reinforced units as milliseconds throughout the program
• Fixed WinNUT titlebar being blank
• The Import Old Preferences File menu item now enables and disables correctly
• UPS variables now default to an obvious out of range value (-1) to indicate that there was a problem retrieving them. I don't have an optimal solution for handling missing variables implemented yet; see #116 for more info
• Battery charge and run time value calculations will also now correctly fail if there are any missing variables required for the calculations

Full Changelog: v2.3.8800...v2.3.8824

Pre-Release v2.3.8800

⚠️ Warning: Important changes to WinNUT preferences system

WinNUT has undergone a fairly important change to its underlying preferences system, that besides an import dialog, should be otherwise unnoticeable.

WinNUT used to store its settings in the User Registry Hive. This was problematic for a number of reasons; the largest one being that I'm moving WinNUT to a new deployment system which would be helped by migrating to the default .NET Framework settings system.

I've created a migration wizard which will pop up the first time you open this version of WinNUT. It will ask you what you would like to do with the old settings; Import, Backup (save a copy), Delete, or do nothing and use a fresh copy of the Settings. Besides the Delete option, this process is entirely non-destructive and will leave your old preferences as they were in the Registry. As long as an old copy of WinNUT preferences remain in the Registry, there will always be an option in the File menu that will restart the migration wizard. I've tested this several times on my own system, and everything appears to be working as intended. Please comment in the Discussion if you experience any problems, or have any questions.

WinNUT 1.x Import procedure

Up until this release, WinNUT used to have an option for importing WinNUT 1.x settings into its Preferences registry system. I removed this feature as of now since I believe most people are currently running WinNUT 2. If you have WinNUT 1.x settings that you wish to carry over, you may then download the release prior to this one, launch it, run the 1.x import procedure, exit, then update to this version and follow the migration wizard as previously described.

🌐 Translators needed!

If you are proficient at translating from English to another language, please consider contributing a translation to this project. Several new strings have been added, while existing ones need review. It's a great way to contribute back to this project and benefit other users.

What's Changed

• Upgrade to .NET Framework Settings System by @gbakeman in #114

Full Changelog: v2.3.8754...v2.3.8800

Pre-Release v2.3.8754

First pre-release of the 2.3 cycle.

What's Changed

• Correct FormatException when parsing Invariant-locale numbers in user's locale by @gbakeman in #125
  • This will fix immediate disconnects people were experiencing with non-en* locales.

Full Changelog: v2.2.8719...v2.3.8754