Releases: nutdotnet/WinNUT-Client
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
Contributors
Assets 4
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
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
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
FormatExceptionwhen 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
Contributors
Assets 4
Release v2.2.8719
Introduction
After thirty-three months since the last release v2.0.7722.30975, with work by @gawindx, myself and several other contributors to the WinNUT project, I'm proud to offer the latest stable release of WinNUT. This marks the first stable release since @gawindx kicked off the effort to modularize WinNUT and improve maintainability and stability. Unfortunately we've lost contact with them, but I decided to take over and relocate the project in an effort to leave WinNUT in a stable and efficient state. I hope you find this release meeting your expectations and needs for UPS monitoring.
Functional/event handling improvements
Many functional changes under the hood have been made to WinNUT, starting with the code modularization kicked off by @gawindx. Further work was done to improve & fix handling power event changes, connection changes and other events from the UPS. Windows 10+ notifications should now be working, as well as the stop action system and Full Shut Down commands from the UPS. The Error Reporting system is more stable, and the automatic reconnection system is fully working. UPS Load calculation has also been reworked.
- Windows 10 Hibernate & Clear Shutdown Timer (redo) in #7
- Improve Connection handling & Logging, Power State handling in #11
- Better disconnection handling in main form in #20
- Large changes to Socket/UPS, DATA-STALE error handling in #25
- Battery-related changes in #33
- Re-activate stop actions system and status updates overhaul in #36
- Correct Interval/Delay value in #37
- Fix incorrect windows version detection in #51
- Fix List_Var_Gui error in #52
- Upgrade unhandled exception handling, cryptography in #49
- Respect Follow FSD setting in #57
- Improve connection loss handling in #64
- Define UPS_States values as pow of 2 to fix state change detection by @supersmile2009 in #71
- Improvements to Login subroutine in #88
- Error Reporting & Exception Catching Refactor in #86
- Fix FormatException in Update_Gui in #98
- Fix unable to exit with tray closing functionality in #108
- Re-enable retry connection on first start in #107
- Correct UPS Load display in #112
Setup and deployment
Work was done to change how WinNUT was deployed, from simple changes to the Setup project builder to the deployment of a debug Continuous Integration system for making debug builds automatically for pull requests. WinNUT was also upgraded to use the .NET Framework version 4.8. This is the latest version that still has Windows 7 SP1 as the minimum system requirement.
- Creating Continuous Integration workflow in #28
- Installer dependency cleanup in #48
- Upgrade to .Net Framework 4.8 in #53
- Fix release build by @supersmile2009 in #72
- Update README.md by @pvanderp in #87
Logging improvements
How and where WinNUT stores log files has been standardized against the .NET Framework so they can be predictably found in (user folder)\AppData\Roaming\NUTDotNet\WinNUT Client\(version)\Logs.
- Logging Improvements in #10
- Additional logging improvements and cleanup in #19
- Logging fixes in #50
- Attempting to finally solve data directory oddities in #62
- Fix logs going to App directory again in #111
Translation improvements
Our international audience has been busy improving translations for WinNUT. A bug causing errors when strings were too long was fixed. If you see translations that need additional work, please consider contributing.
- Improve de-DE (German) Translation in #8
- Add Translation/zh-TW/zh-TW.csv for Chinese (Traditional) by @yrctw in #23
- Small updates to german Translation by @MartinKurtz in #30
- Applying translations in #39
- Update translation for Traditional Chinese by @yrctw in #119
New Contributors
- @yrctw made their first contribution in #23
- @MartinKurtz made their first contribution in #30
- @andriibratanin made their first contribution in #54
- @supersmile2009 made their first contribution in #71
- @pvanderp made their first contribution in #87
Full Changelog: v2.0.7722.30975...v2.2.8719
Addendum/Closing words
From the onset, I thought my efforts would be simply to fix bugs in WinNUT and leave it otherwise unchanged. Afterwards, I would begin work on WinNUT's replacement. As time goes on, I'm realizing that there's more work I'd like to do on WinNUT to leave it in the best possible state, as well as attempt to integrate the NUT.Net library I've been working on in preparation for the next version of WinNUT. Thus, I'm now planning on several more stable releases of WinNUT before I officially consider the project complete and deprecated. Please continue providing your feedback and bug reports so we can make this iteration of WinNUT the most complete and bug-free iteration yet.
Contributors
Assets 4
Pre-Release v2.2.8693
What's Changed
- Fix logs going to App directory again in #111
- I'm moving WinNUT towards following .NET Framework standards. This change will put the logs in yet a new folder structure:
(user folder)\AppData\Roaming\NUTDotNet\WinNUT Client\(version)\Logs.
- I'm moving WinNUT towards following .NET Framework standards. This change will put the logs in yet a new folder structure:
- Correct UPS Load display in #112
- Introduces a new system of retrieving or calculating the load on the UPS, and removes any reference to the Load calibration values and Load dial adjustments. My hope is to account for as many UPSs as possible, but if this breaks something for you, please comment in #41 with a full Debug log, UPS Variable output, and current real power usage attached and I'll try to help.
Full Changelog: v2.2.8690...v2.2.8693
Pre-Release v2.2.8690 (minor fix)
What's Changed
- Quick release that fixes log files being directed to the application directory. Log files now follow standard .NET Framework directory conventions and can be found in AppData/Roaming/NUTDotNet/WinNUT Client/(current version)/. #110
- Some additional small code changes have been made that should not affect functionality.
Full Changelog: v2.2.8688...v2.2.8690
Pre-Release v2.2.8688
What's Changed
- Fixed being unable to exit when close and minimize to tray were enabled. WinNUT now exits normally in all circumstances.
- in #108
- Re-enabled the auto-retry functionality when starting WinNUT for the first time. I had disabled it because WinNUT hangs while making a connection. Hoping to address that in the future.
- in #107
Note: There was an issue where the installer I uploaded here contained outdated code. I'm not sure why, but it's been fixed now. If you managed to download the broken installer, please uninstall WinNUT, redownload the installer here and reinstall WinNUT.
Full Changelog: v2.2.8617...v2.2.8688