Audials One 歷史版本列表
更新時間：2020-02-04
更新細節：
更新時間：2020-01-30
更新細節：
更新時間：2020-01-30
更新細節：
What's new in this version:
- Fixed type cast problems with Gyro output curves. Fixed Easeout Cubic curve for Gyro controls
- Added output mouse speed text next to mouse sensitivity
- Actually added mouse sensitivity binding in Profile Editor. Major Oopsie
- Fixed switching of DInput only profiles
- Changed display of rumble edit controls
- Change main window init to launch background tasks later
- Change to allow HidGuardian message to appear in Log tab
更新時間：2020-01-30
更新細節：
更新時間：2020-01-29
更新細節：
What's new in this version:
- Fixed profile duplication
- Add log message if HidGuardian is detected
- Change to launch HidGuardHelper later at startup
- Fixed midpoint for Swipe to Axis controls
- Added comment in profiles stating which version of DS4Windows made the file
- Added link to HTML5 Gamepad Tester under Utils
- Change to apply trigger max zone when dead zone is 0.0
- Updated Russian translation. Change provided by DragonZX
- Fixed exclusive mode issues for non-admin users. Fixed second instance shutdown failure.
- Added extra hooks in Binding window for Numpad keys
更新時間：2020-01-28
更新細節：
更新時間：2020-01-25
更新細節：
What's new in this version:
Improvements for plugin authors:
- Finalize property value only when the value is queried
- In previous Gradle releases, certain Gradle types, such as Property or ConfigurableFileCollection, provided a finalizeValue() method that eagerly calculated the final value for a property and prevented further changes.
- When a task starts running, Gradle automatically finalizes task properties of these types, so that the same value is seen by the task's actions and Gradle's build caching/up-to-date checks. This also avoids calculating the property value multiple times, which can sometimes be expensive. Plugins can also use finalizeValue() to finalize other properties, such as a property of a project extension, just prior to querying the value.
- In this release, these types gain a new finalizeValueOnRead() method. This method is similar to finalizeValue(), except that the final value is calculated when the value is queried rather than immediately. Plugins can use this method when a property value may be expensive to calculate or when the value may not have been configured to ensure that all consumers of the property see the same, final, value from that point onwards
- Please see the user manual for more details
New managed property types:
- Gradle 5.5 introduced the concept of a managed property for tasks and other types, where Gradle provides an implementation of the getter and setter for an abstract property defined on a task, project extension, or other custom type. This simplifies plugin implementations by removing a bunch of boilerplate.
- In this release, it is possible for a task or other custom type to have an abstract read-only property of type DomainObjectSet<T>.
- Please see the user manual for more details
New factory methods:
The ObjectFactory type, which plugins and other custom types use to create instances of various useful types, has several new factory methods to create certain Gradle types that could only be created using internal APIs in previous releases:
- The polymorphicDomainObjectContainer() method to create ExtensiblePolymorphicDomainObjectContainer<T> instances
- The namedDomainObjectSet() method to create NamedDomainObjectSet<T> instances
- The namedDomainObjectList() method to create NamedDomainObjectList<T> instances
- Please see the user manual for more details
- Improvements for Gradle tooling providers
Tooling API:
- TestLauncher can run specific Test task tests
- The TestLauncher interface in the Tooling API could already launch tests by specifying the name of the test classes or methods; however, if there are multiple Test tasks, then all Test tasks would be executed
- For IDEs, developers usually want to execute only one task at a time. Gradle 6.1 introduces a new API to execute tests with specific Test task using the withTaskAndTestClasses() and withTaskAndTestMethods() methods
- Fixed issues
4 issues have been fixed in Gradle 6.1.1:
- Gradle 6.1 generates an empty .gradle and gradle directories on each execution in subproject directories
- Memory regression when resolving large artifacts while computing checksums
- Missing fixed issues from Gradle 6.1 release notes
- Plugins using kotlin-dsl and compiled with 6.1 are incompatible with Gradle 6.0
更新時間：2020-01-25
更新細節：
What's new in this version:
- Created Max Output setting for some axes. Replacement for negative deadzone functionality from Jays2Kings build
- Increased stick mouse offset
- Increased virtual controller change delay time
- Fixed saving of Custom Steam Folder setting
更新時間：2020-01-24
更新細節：
What's new in this version:
- fixed a bug that caused some characters to be displayed incorrectly in some cases, e.g. U+2019 Right Single Quotation Mark
- AES encryption is now supported, with key lengths of either 128 or 256 bits. Click here for more information
更新時間：2020-01-20
更新細節：
What's new in this version:
- Added Italian translation file to VS project
- Fixed Y buffer clearing in trackball routine
- Make new Special Actions enabled in the current profile by default
- Make sure to actually load Linked Profiles at program start. Oopsie
- Save settings on log off or Windows shutdown
- Save settings on controller unplug. Needed to save Linked Profile setting
- Link to ViGEm installer version 1.16.116
- Allow moving auto profile entries. Change contributed by mika-n
- Added tooltip to auto-profile path and title editbox fields
- Czech translation added. Provided by Maikeru007
- Fixed binding for Flash at High Latency setting