Releases: nutdotnet/WinNUT-Client
v2.3.9492
Over a month has gone by before releasing what was supposed to be another "quick fix". Thanks again to everyone who has been patiently waiting for this one.
What's Changed
- Protocol, error handling, other improvements in #230
- Fixes UI becoming frozen when connection is suddenly disconnected
- Communication timeout is now 5 seconds making broken connections detectable faster than before (timeout was about 30 seconds.)
- NOTE: Communication is still synchronous with the UI so WinNUT will appear to hang during any socket operations (connect, read or write).
- Connection error handling is more consistent
- Fixes bug where data was not available untill the next poll/update.
- New copy and save commands for List_Var_Gui, handle locked Clipboard in #229
- Overhauled Copy (to Clipboard) command
- Catches any raised exceptions now
- Added new Save (to file) command, with other general improvements
- Deleted Clear button and function
- Errors encountered while copying or saving are logged to file, the messages list and displayed in a
MessageBox. - Add
ToolTipcontrol and text for buttons - Add resource strings for localization
- Encrypted data validation, logging/data storage enhancements in #231
- Enhanced old Registry parameter data detection
- Verify encrypted data can be decrypted (username/password), and write a line to the displayed logs if an error was encountered.
- Enhanced the displayed logs system. String format is slightly different, maximum number of lines is defined in the Logger class, prune old lines when maximum is met, and make sure the displayed form is updated on launch.
- Some modifications to the crash handler, should be more reliable.
- Add -PersistDataInStartupPath Command Line Argument, which causes WinNUT to try to store persistent date (logs) in its startup path. By default, WinNUT will store data in a dedicated directory in the local AppData folder.
- Crash logs now write to the above directory.
- Prefs Gui displays a log when preferences are changed.
- Connection menu item states are more consistent
- Overall WinNUT UI state should be more consistent as well.
Full Changelog: v2.3.9452...v2.3.9492
v2.3.9452
Quick update going out to address a race condition in #223. I'm afraid I haven't been able to completely isolate it, but this update brings some major changes to the socket and connection code that should make WinNUT more stable over all. Special thanks to @yoyoma2 for their knowledge and patience as we worked through the issue.
What's Changed
Full Changelog: v2.3.9437...v2.3.9452
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
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
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
