Release 0.3.1
Overview
This release mainly focuses on fixing major bugs from the previous version, as well as some minor detail corrections. For specific information, please refer to the Changelogs
section below.
please note
Although the release assets of this version include multi-platform packages, it does not mean that KeyTone already supports multiple platforms.
At this stage, the main focus is still on feature development, and this process is carried out under Windows.
In other words, this version of the KeyTone package only guarantees the usability and functionality completeness of the software under Windows. The packages for other platforms only follow the most basic build packaging and have not undergone any related testing.
When will other platforms besides Windows be supported?
A: The current version has not been officially adapted for Linux and MacOS platforms. We expect to consider formal adaptation work after version 1.0.0.
Security
The SHA256 hash sum
KeyTone-0.3.1-win-x64.exe
is:
9b9f526a24af46be275e03f04961a2ee5c578b8826584f609301a199783901fc
KeyTone-0.3.1-linux-x64.tar.gz
is:
0fc1aa9cd4d6d58e5dbe2febecf5e41af441cde531ed6a9a133d18cc76facde7
KeyTone-0.3.1-linux-x64.AppImage
is:
d57df68364dfc6df42bf2490601831027ff58220f426006c627b31fcd2522acb
KeyTone-0.3.1-linux-x64.deb
is:
d9418a821acb088eb2ff91a2a63533222799ba634d4e2429b53035f5064321ba
KeyTone-0.3.1-mac-x64.dmg
is:
291c8be72a61d5dbda732e7dbd4a96a0454f0118429ede41fd4fc3d0d8f509ad
KeyTone-0.3.1-mac-arm64.dmg
is:
a037f8d32971a2bf9a231ee5d27046ae0483b12a1eac05a6f70580f765cbe7bb
The MD5 hash sum
KeyTone-0.3.1-win-x64.exe
is:
83b581173221a9dfbe3d614245054cbb
KeyTone-0.3.1-linux-x64.tar.gz
is:
6dc7986a1b382d99bf87fc04462df5dc
KeyTone-0.3.1-linux-x64.AppImage
is:
d0d3a7f6eb6c605d1b6db6a7a5f5eb9a
KeyTone-0.3.1-linux-x64.deb
is:
bc6e6b72d328ae9fb11515ae1e50f8c7
KeyTone-0.3.1-mac-x64.dmg
is:
3ab7e182dbc0ebe324a849b9d0f5edc6
KeyTone-0.3.1-mac-arm64.dmg
is:
15c4dbfbc890ede0ffcf385cb7b4827d
Changelogs
Bug Fixes
- sdk: Verified that even if the key sound package does not exist, it will not cause errors, and the situation where the selected key sound package is an empty string during initialization can actually be classified as such. Therefore, there is no need for the SDK to return an error for an empty string in the RESTful response. (75d8dce), closes #56
- ui: Resolved the issue where the focus remained on the selection component after the user selected a key sound package on the main interface, which could easily lead to accidental touches. (c45c4bd), closes #56
- ui: Fixed the issue where the interface would freeze when the key sound package list was empty. (e2dbf2d), closes #56
- ui: Fixed the issue where the key sound package list did not update to the latest after the user created a new key sound package and returned to the main page. In this commit, the initialization logic of the key sound package list was moved to the App.vue file where it belongs. (6f94635), closes #56
- ui: Provided a quick button on the main interface to clear the selected key sound package, solving the problem where the selected key sound package could not be cleared to the software's initial state after selection. (8db1a47), closes #56