Evernote 歷史版本列表
更新時間：2019-07-23
更新細節：
What's new in this version:
MONITORING:
- Huge update to the monitoring engine - better readings, newer CPU support
- Updated how the default sensors are picked. New algorithm avoids selecting sensors with readings above max threshold for temperatures
CPU:OCCT:
- Auto mode now disables AVX by default on AMD CPU in all data set sizes
MAIN:
- increased the waiting screen width to fit most translation in one line for looks
Translations:
- Added Japanese
- Added Chinese (Simplified)
- Added Chinese (Traditional)
- Added Swedish
更新時間：2019-07-11
更新細節：
What's new in this version:
- UI: Main window is now fully resizable
- Monitoring: added Min/Max value colums in table view
- Main: Improved license and .lang file detection speed
- Main: Fixed a bug with some .net framework that are missing a particular registry function
- Main: Fixed an issue where OCCT could crash at startup when no graphic card driver was installed
- Main: Fixed a display bug with test durations over 24 hours
- Translations : Fixed a bug where putting a corrupt English.lang file next to OCCT.exe could crash the app
更新時間：2019-06-27
更新細節：
What's new in this version:
- CPU:OCCT : fixed an issue where small data set might trigger an exception on some Ryzen CPUs
更新時間：2019-06-26
更新細節：
更新時間：2019-06-26
更新細節：
更新時間：2019-06-25
更新細節：
What's new in this version:
Bugs fixed:
- "Single radio button" form component: In console mode, the selection script for a button was called twice if the button was not initially selected
- Since install4j 7.0.10, a security fix prevented launchers from running on unpatched Windows 7 installations. This has been fixed for Java 9+ and recent Java 8 versions.
- File installation options of files in the distribution tree that were also added on the "Installer->Custom Code & Resources" step were ignored
- The dialog for showing running processes did not have the install4j window icon
- Fixed NPE when a custom installer application was started in-process from a modular application
- Linux/Unix: When a service script was executed with the "start" parameter, the single instance check was not performed
- Background update downloader: Downloaded media files of previously successful updates could not be deleted if the API was used in a particular way. Now they are deleted by the "Schedule update installation" action.
- macOS: When using JavaFX and an automatic launcher integration that checks for visible windows, the AWT was initialized even if the update downloader was started as an external process which could lead to a deadlock for recent Java versions
- macOS: The installer variable sys.preferredJre could hold the wrong path
- macOS: Command line launchers in archives could not find bundled Java 9+ JREs
- Windows: Native install4j runtime files were not overwritten when an older installation was installed on top of a newer installation
更新時間：2019-06-25
更新細節：
What's new in this version:
Bugs fixed:
- "Single radio button" form component: In console mode, the selection script for a button was called twice if the button was not initially selected
- Since install4j 7.0.10, a security fix prevented launchers from running on unpatched Windows 7 installations. This has been fixed for Java 9+ and recent Java 8 versions.
- File installation options of files in the distribution tree that were also added on the "Installer->Custom Code & Resources" step were ignored
- The dialog for showing running processes did not have the install4j window icon
- Fixed NPE when a custom installer application was started in-process from a modular application
- Linux/Unix: When a service script was executed with the "start" parameter, the single instance check was not performed
- Background update downloader: Downloaded media files of previously successful updates could not be deleted if the API was used in a particular way. Now they are deleted by the "Schedule update installation" action.
- macOS: When using JavaFX and an automatic launcher integration that checks for visible windows, the AWT was initialized even if the update downloader was started as an external process which could lead to a deadlock for recent Java versions
- macOS: The installer variable sys.preferredJre could hold the wrong path
- macOS: Command line launchers in archives could not find bundled Java 9+ JREs
- Windows: Native install4j runtime files were not overwritten when an older installation was installed on top of a newer installation
更新時間：2019-06-23
更新細節：
更新時間：2019-06-15
更新細節：
更新時間：2019-06-14
更新細節：