Difference between revisions of "Version 3.3 (WinX)"

Revision as of 15:14, 24 September 2018

A new control for viewing documents with 3D content was added. It allows basic pinch/zoom/selection actions with touch and mouse and currently supports .obj, .3ds and .stl formats, without textures. It is now the default document viewer for UBK documents with .obj extension, both in DetailsPage as well as DocumentsPage.
It is now possible to toggle the camera flashlight from all camera related pages (POI View, Scan View, etc.).
The Developer Mode has a search feature now and additionally displays declared Converters
AR-Markers can now be used with Windows-based devices
It is now possible to show Billboards in relation to AR-Markers.

The in-app PDF viewer now re-renders documents after zooming to provide better readability.
UBIK now actively clears out cached properties to reduce its memory footprint. See Fast Startup - Technical background for more details.
Further reduced the memory consumption for local content. (More properties are only loaded on demand.)
UBIK now requires far less memory during initialization and branch downloads.
It is now possible to customize the Elements of the Geo Edit Control and the Document Page Sidebar and Flyout.
Improved the usability of offline branch download by dividing an entire branch download task into several smaller ones.
Improved startup time of camera-related views (POI View, Scan View).
Improved browsing performance in developer mode.
Improved the file uploading mechanism (e.g. less web traffic, more reliable retries upon failures).

Fixed an issue, where the Annotate and Hotspotting button were enabled on non-classified documents.
Fixed an issue, where the FlipView was not updated once the content was loaded.
Fixed an issue, where no visual feedback was given when clicking on Child Items.
Fixed an issue where files are downloaded unnecessarily for documents being deleted.

@@ Line 17: / Line 17: @@
 * Improved browsing performance in developer mode.
 * Improved the file uploading mechanism (e.g. less web traffic, more reliable retries upon failures).
-* If loading of a custom XAML template fails, the full error message (incl. line number) is now displayed in the crossed-out section
+<!--* If loading of a custom XAML template fails, the full error message (incl. line number) is now displayed in the crossed-out section
-* If loading of a custom XAML template fails, the file as well as the type browser are directly accessible from the error template (analog to [[Developer Mode]])
+* If loading of a custom XAML template fails, the file as well as the type browser are directly accessible from the error template (analog to [[Developer Mode]])-->
 [[Category:Version 3.3|Version 3.3 (WinX)]]