DesktopOK (64-bit) 歷史版本列表
更新時間：2020-11-06
更新細節：
What's new in this version:
New:
- Thunderbird prompts for an address to use when starting an email from an address book entry with multiple addresses
Fixes:
- Searching global search results did not work
- Link location was not focused by default when adding a hyperlink in message composer
- Advanced address book search dialog was unusable
- Encrypted draft reply emails lost "Re:" prefix
- Replying to a newsgroup message did not open the compose window
- Unable to delete multiple newsgroup messages
- Appmenu displayed visual glitches
- Visual glitches when selecting multiple messages in the message pane and using Ctrl+click
- Switching between dark and light mode could lead to unreadable text on macOS
更新時間：2020-11-06
更新細節：
What's new in this version:
- Support Android 11
- Call of duty：Smart keys to realize one-key medicine, please download the official VIP keymapping（VIP）
- You can change different skin colors for TC Games（VIP）
- You can change different mouse styles in TC Games（VIP）
- Added the function of remove black borders on the screen, which will stretch the image to fill the black borders when full screen or maximized（VIP）
- Added the laconic mode, you can one-click to hide the upper and right toolbars of the software（VIP）
- You can also use smart keys when you set the resolution to 640 or 480 in the TC Games（VIP）
- Added the macro command ‘press down’ in the macro key（VIP）
- Added the custom toolbar function, you can decide which buttons to display and their order
- Added the connection record for Wi-Fi connection , you can click the connection history record to connect the phone directly
- Added a button to disable all shortcut keys in the input settingsYou can also set shortcut keys for back, homepage, recent task
- Optimize the MOBA games such as League of Legends: Wild Rift ,smart casting is not interrupted when using continuous click keys
- Optimize the search function of keymapping center
更新時間：2020-10-30
更新細節：
What's new in this version:
- This version fixes various regressions and improves stability
更新時間：2020-10-27
更新細節：
What's new in this version:
- New Project Import interface and improved functionality
- Revamped Project Sync for easier, smoother timeline updates
- Remap columns when importing from MS Project
- Filter data to view and import strictly what you need from Project
- See your tasks’ hierarchy from Project when importing or syncing
更新時間：2020-10-22
更新細節：
What's new in this version:
New:
- MailExtensions: browser.tabs.sendMessage API added
- MailExtensions: messageDisplayScripts API added
Changes:
- Yahoo and AOL mail users using password authentication will be migrated to OAuth2
- MailExtensions: messageDisplay APIs extended to support multiple selected messages
- MailExtensions: compose.begin functions now support creating a message with attachments
Fixes:
- Thunderbird could freeze when updating global search index
- Multiple issues with handling of self-signed SSL certificates addressed
- Recipient address fields in compose window could expand to fill all available space
- Inserting emoji characters in message compose window caused unexpected behavior
- Button to restore default folder icon color was not keyboard accessible
- Various keyboard navigation fixes
- Various color-related theme fixes
- MailExtensions: Updating attachments with onBeforeSend.addListener() did not work
- Various security fixes
更新時間：2020-10-16
更新細節：
更新時間：2020-10-15
更新細節：
What's new in this version:
Performance improvements:
- File system watching is ready for production use
- In an incremental build, input and output files are checked to determine what needs to be rebuilt. This feature typically saves a lot of time; however, it adds some I/O overhead, which can be noticeable in large projects when not much has changed since the previous build.
- Back in Gradle 6.5 we've introduced file-system watching as an experimental feature. When enabled, it allows Gradle to keep what it has learned about the file system in memory during and between builds instead of polling the file system on each build. This significantly reduces the amount of disk I/O needed to determine what has changed since the previous build.
- This feature is now ready for production use and supported on Linux, Windows and macOS. You can enable it by adding the following to gradle.properties in the project root or in your Gradle user home: org.gradle.vfs.watch=true
Configuration cache improvements:
- Gradle 6.6 introduced configuration caching as an experimental feature. This release comes with usability and performance improvements for the configuration cache.
- Early adopters of configuration cache can use the command line output and HTML report for troubleshooting. Previously, the configuration cache state was saved despite reported problems, which in some situations required manual cache invalidation. In this release, the configuration cache gets discarded when the build fails because of configuration cache problems. Note that you can still ignore known problems.
- The problem report is also more helpful now. It reports the source of problems more accurately, pointing at the offending location in plugins and scripts in more cases.
- Loading from the configuration cache is also faster and memory consumption during builds has been reduced, especially for Kotlin and Android builds.
- Read about this feature and its impact on the Gradle blog. You can also track progress of configuration cache support in core plugins and community plugins.
New JVM ecosystem features:
- Toolchain support for JVM projects
- By default, Gradle uses the same Java version for running Gradle itself and building JVM projects.
- This is not always desirable. Building projects with different Java versions on different developer machines and CI servers may lead to unexpected issues. Additionally, you may want to build a project using a Java version that running Gradle is not compatible with.
- Before this release, it required several steps to configure a different Java version for compilation, testing, generating Javadoc, and executing applications.
- This release introduces the toolchain concept to simplify such a setup. A Java toolchain is a set of tools (javac compiler,java command etc), taken from a local Java installation and used during the build. Instead of manually specifying executables for the various tasks, toolchains provide a centralized place to define the Java version requirements in the build.
New dependency management features:
- Compile-only API dependencies for JVM libraries
- When writing a Java (or Groovy/Kotlin/Scala) library, there are cases where you require dependencies at compilation time which are parts of the API of your library, but which should not be on the runtime classpath.
- An example of such a dependency is an annotation library with annotations that are not used at runtime. These typically need to be available at compile time of the library's consumers when annotation processors inspect annotations of all classes. Another example is a dependency that is part of the runtime environment the library is expected to run on, but also provides types that are used in the public API of the library.
- The Java Library Plugin now offers the compileOnlyApi configuration for this purpose. It effectively combines the major properties of the compileOnly configuration (dependency will not be on the runtime classpath) and the api (dependencies are visible for consumers at compile time).
Other new features and usability improvements:
- Abbreviation of kebab-case project names
- Gradle allows you to abbreviate project and task names from the command-line. For example, you can execute the task compileTestJava by running gradle cTJ.
- Up until this release, fuzzy name matching only worked for camelCase names (e.g. compileTestJava). This is the recommended convention for task names, but it is unusual for project names. In the Java world, directory names are usually all lowercase by convention and in Gradle, project names usually follow the name of the directory the project is in.
- Many projects worked around this limitation by using kebab-case project directories (e.g. my-awesome-lib) while defining different camelCase project names in their settings scripts. This allowed them to use project name abbreviations in the command line but added additional complexity to the build.
- This release changes the fuzzy name matching to support for kebab-case names. Now, you can execute the compileTestJava task in the project my-awesome-lib with the following command
Fixed:
- Make <feature>RuntimeElements extend <feature>RuntimeOnly
- Only log file events that cause a change in the virtual file system
- Introduce file system watching debug flag
- Improve verbose VFS logging
- Update InProcessGradleExecuterIntegrationTest for file system watching
- Remove ToBeFixedForFileSystemWatching annotation
- Allow repository definition by configuration
- Add single/multi-project choice to 'gradle init --type application'
- Add 'compileOnlyApi' configuration to java-library projects
- TestNGTestFramework makes the Test Retry plugin incompatible with config cache
- Add switch to enable verbose logging for VFS
- Dependency resolution selector cache not specific enough for virtual platform edges
- Scala compilation of protobuf generated code is broken because zinc leaks protobuf-java to compile classpath
- Let user configure JavaCompile with source/target/release independant of a toolchain
- Performance bottleneck for large projects when file system watching is enabled
- Let `Javadoc` task accept a toolchain
- Remove incubating message about watching the file system
- Drop "unsafe" from file system watching-related property names
- Allow configuring the maximum number of watched hierarchies
- Change 'gradle init' to generate multi-projects
- Provide API to query for toolchains
- Extend name matching section in user guide
- RepositoryContentDescriptor should support include/exclude version ranges
- Verify project naming convention consistency
- Make use of kebab case name matching in gradle/gradle
- Precompiled script plugins - `GradleProperties has not been loaded yet.`
- Let `JavaExec` task accept a toolchain
- build events generated by tooling api are wrong when OperationCompletionListener is used
- Make fuzzy matching work with kebab-case project naming
- Use composition instead of inheritance to separate BuildOperationRunner from BuildOperatoinExecutor
- Configuration caching uses stale provider value
- Configuration caching querying task outputs too early
- Toolchain is matched deterministically
- Download toolchains on demand
- Use Kotlin source in Santa Tracker Kotlin Android performance tests
- Detect common Java installation locations
- Let `Test` task accept a toolchain
- Ability to configure toolchain requirements for a build
- Deprecate `JavaApplication#setMainClassName` in favour of property
- Enable partial VFS invalidation by default
- Move excessive logging around VFS to build operations
- Explain memory leak-like slowdown when FSW is enabled on Gradle build
- Support for compiling own (test) code with Groovy 4.0
- Gradle 6.5 pulls in optional dependency
- Gradle 6.5 build fails on Java 15-ea with Execution failed for task ':jar'. java.util.ConcurrentModificationException (no error message)
- Memory inefficiency in ConsumerVariantMatchResult for very large project.
- Pre-existing empty output directory may cause incorrect up-to-date checks
- JDK 15 support in Gradle
- Update integration tests using Jetty to run on JDK15
- Jacoco JDK15 support
- Review how TestKit directories are watched
- Disable file system watching when there is a change to Ant default excludes
- Verify correct usage of FileTimeStampInspector when file-system watching is enabled
- Use the Java API compiler when possible
- Attribute "without_test_code" is missing in .classpath file for project references
- Support `SUBST` or disable its use with file watching
- Test filters hide underlying issues during test task execution
- Add test for continuous build with VFS retention enabled
- Tooling API on JDK11 can not connect to Gradle project 4.5
- Feature? dependency lock missing skippedDependencies Property
- Composite artifact can't be resolved in buildSrc
- Maven2Gradle conversion support targeting Kotlin DSL
- Detect local Java installations
- Java toolchain detection should work on macos when no system VM installed
- Artifact transforms with dependencies fail when project substitutes external one
- Samples use nightly build instead of RC
- 6.7-rc-1: build fails with Cannot acquire state lock for project
- Property auto-detect used at configuration time when using toolchain with auto-download=false
- Service creation is too eager
- Javadoc and toolchain: task is up-to-date when toolchain changes
- `Problems reading data from Binary store` with intra-project dependency and capability resolution strategy
- Incremental annotation processing can fail when forking with Java 8
- Incremental compilation wipes out aggregating processor file in Gradle 6.7
更新時間：2020-10-14
更新細節：
What's new in this version:
- Added NVidia RTX 3090 + 3080 + 3070 GPU support, adjusted SIV to compensate for the NVidia driver misreporting the AI Tensor Core count.
- Added Windows 10 21H1 Build 20236 support. Enabled operation of [ACPI Eval], etc..
- Added support for voltages reported via the MSI Mystic Light controller.
- Added CentaurHauls CHA memory controller speed + timing information and Dual Socket system support.
- Adjusted AMD Athlon M1 (Argon) + M2 (Pluto) + M2 (Orion) K7 MSR reporting.
- Added AMD 756 SMBus + VIA KT880 chipset support.
- Added Abit KW7 + ASUS Rampage VI Extreme Encore + TUF Gaming X570-Plus + BIOSTAR B350GT5 + Centaur CHA006 + DFI LP UT X58 + EVGA 134-KS-E377 + Gigabyte 7IXE + MSI MS-7A40 (B450I Gaming Plus AC) + MS-7576 (880G-E45) + MS-7B12 (MEG Z390 Ace) motherboard support.
更新時間：2020-10-14
更新細節：
What's new in this version:
- Version 5.2 provides visualization and performance enhancements. Updates include GC content visualization, support for finding similar DNA sequences, simulation of supercoiled DNA migration in agarose gels, support for ssDNA sequences, and Sequencher file import.
GC Content Display:
- A GC content color or line plot can now be displayed in Map view, and bases can be colored by GC or AT in Sequence view
Find Similar DNA Sequences:
- When searching for DNA sequences, imperfect matches containing gaps or mismatched bases can be found, and search performance has been optimized
Supercoiled DNA Migration:
- When simulating agarose gels, the migration of uncut circular sequences can be visualized, and supercoiled MW markers can be used
ssDNA Sequences:
- A single-stranded DNA (ssDNA) sequence can now be created or imported, with support for feature annotation and sequence manipulations
Optimized History View:
- When editing sequences, the history is compressed to allow efficient storage as well as Undo for large sequences
- Additional Protein Feature Types
- The set of supported protein feature types has been extended, including support for the misc_feature type
Sequencher File Import:
- Sequencher files can now be imported into a SnapGene collection
更新時間：2020-10-12
更新細節：