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.
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.
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.
Beginning with the (now releases) Version the
Method BoundingBox#extendMargin of VTM was corrected in its behavior.
From now on, it exposes three overloads:
BoundingBox extendMargin(float margin)
BoundingBox extendMargin(float marginX, float marginY)
BoundingBox extendMargin(float marginLeft, float marginRight, float marginTop, float marginBottom)
for a better and more dynamic usage of this feature.
Also the value margin was changed from maximum randomness in behavior (it was a factor that was somehow based on the original boundingbox, but not really undestandable) to percent. So extendMargin(50) will extend the original BoundingBox by 50% of its original size into all directions.
Also it now accepts negative values to shrink the orignal Box.
For further details click here.
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.
building_has_features view.The Vue3 re-implementation has gone live today.
The App features many new highlights like:
Check it out live.