5 Posts getaggt mit "features"

Changelog (1.39.X ➔ 1.40.0)​

API Usage​

This update aims for enhanced stability and more unified util interfaces.

The FileController has been enhanced to work with unified rpc requests in the same way as it does with URLEncoded Multipart Fileuploads.

Also it allowes more features for dynamical usage such as receivedFiles to check if the FileController did prepare any uploaded files, accepting an optional parameter to check for a specific transferred file.

Also its usage with internal-api has been simplified and streamlined.

Accessibilty Reporter​

The latest update of the accessibilty reporter allows many new features and bugfixes, that will now allow better administration and preparation of the integration with CE's map.

Changelog (1.38.0 ➔ 1.38.1)​

Routing​

We introduce new intermediate waypoint caching for the routing algorith, that can increase the performance on long and complex routes up to ~8x.

Instead of re-calcuating the distances between nodes in spererate segments, these can now be cached and shared, directly when loading the edge definitons, resul

Also the Viewer for Editor-Sessions was corrected and will show all valid sessions again.

Changelog (1.36.x ➔ 1.37.0)​

With this new Releases, Tags can have a new, optional, setting named showWhileNavigating which can be set to true. If so, these Items (either the Tag's Room or Category Image) should not be hidden while showing any navigation.

Route-Items should be z-indexed higher.

Changelog (1.35.0 ➔ 1.36.0)​

Starting with this Version, the new API Level 19 is introduced, changing structure on the Table tagbase..room_has_content.

There is a new type [field type] called campaign_audio. This type has a special, breaking behavior. It does not implement any actual data, but the field displayname contains the Id if the actual campaign this content should be replaced by.

Therefore the Apps shall display an Audio-Player for this (just like in the Campaigns) playing the defined campagins contents.

To support the migration, the API_STRUCTURE_VERSION will be incremented to 18.

API Version 1.32.0​

Starting from this Version, the API will support a new Feature called readonly. This feature allows the User to execute Methods on a Write-Locked Guide that do not execute any Data-Update.

All Data-Updates will always fail when setting mode to readonly, even when no guide-lock is aquired.

This feature is the API Side implementation auf the new Content Editor's Read-Only Mode.