Difference between revisions of "Version 4.4 (WinX)"
(30 intermediate revisions by 7 users not shown) | |||
Line 12: | Line 12: | ||
= Release Notes = | = Release Notes = | ||
+ | |||
+ | == Release == | ||
+ | |||
+ | ===4.4.21 on 2023-09-04 {{key press|Store}} === | ||
+ | Same as beta 4.4.21. | ||
+ | |||
+ | |||
+ | == Beta == | ||
+ | |||
+ | ===4.4.21 on 2023-08-30 {{key press|Store Beta}} === | ||
+ | * Fixed a crash caused by the back button. | ||
+ | |||
+ | |||
+ | ===4.4.17 on 2023-08-28 {{key press|Store Beta}} === | ||
+ | * General improvements on app stability. | ||
+ | * Fixed an issue where the App randomly crashed when editing tasks in quick succession. | ||
+ | * Fixed a bug where cancelling the editing of a geo property was not reflected in the UI. | ||
+ | * Fixed an issue where the import of broken profiles was not prevented properly. | ||
+ | * Fixed an issue where editing a value on a Guid List Dialog would not be possible on Windows 11. | ||
+ | * Further improved the accuracy of PDF search highlights. | ||
+ | * Fixed an issue where the app could potentially freeze when deleting all profiles. | ||
+ | * Fixed an issue where the InvokeOnItemsCommand could only be applied to selected items. | ||
+ | |||
== Preview == | == Preview == | ||
− | === 4.4. | + | ===4.4.12 on 2023-08-08 {{key press|App Center}}=== |
+ | * Fixed an issue where profiles could not be loaded when the name of the profile was too long. | ||
+ | * Fixed an issue where after editing authentication properties an unwanted backward navigation occurred. | ||
+ | * Fixed an issue where some download indicators were missing on document tiles. | ||
+ | * Fixed some UI issues when trying to edit GeoData or DateTime Properties. | ||
+ | * Fixed an issue where the NavigationView sidebar navigational buttons were clipped on the right edge, and updated its core styles and application in main content areas. | ||
+ | * Fixed an issue where too many root object overlapped the navigational buttons on the sidebar. | ||
+ | * Fixed an issue where only up to 9 root items could be displayed on the root area. | ||
+ | * Fixed a distance calculation error when opening the POI page without a current location. | ||
+ | * Fixed an issue where a Guid link property value appears empty after you close the Guid editor. | ||
+ | * Fixed an issue where the entered property value does not appear to be set if you open the editor while being in a direct edit session at the same time. | ||
+ | * Fixed an issue where saving signatures on unusual display sizes would not be possible. | ||
+ | * Fixed an issue where saving signatures on Windows 11 would not be possible. | ||
+ | * Fixed an issue where the selected property value definition (on offline query criteria) can be lost or incorrectly displayed. | ||
+ | * Partially fixed an issue where PDF text search highlights are sometimes poorly positioned. | ||
+ | |||
+ | |||
+ | === 4.4.10 on 2023-07-19 {{key press|App Center}} === | ||
* Fixed an issue where the wrong page might be displayed when you navigate to a PDF hotspot. | * Fixed an issue where the wrong page might be displayed when you navigate to a PDF hotspot. | ||
* Fixed an issue where the PDF hotspot is not highlighted when you navigate to it. | * Fixed an issue where the PDF hotspot is not highlighted when you navigate to it. | ||
+ | * Fixed an issue where predefined search texts are not automatically highlighted for certain complex PDF documents. | ||
Line 54: | Line 95: | ||
* During PDF annotating/hotspotting, changes are lost if you leave the page without deselecting the changed annotation/hotspot. | * During PDF annotating/hotspotting, changes are lost if you leave the page without deselecting the changed annotation/hotspot. | ||
* Free Text Annotations that where created in former sessions cannot be selected and therefore cannot be edited any more. | * Free Text Annotations that where created in former sessions cannot be selected and therefore cannot be edited any more. | ||
− | |||
<br/> | <br/> | ||
+ | |||
+ | |||
+ | |||
+ | |||
= ⚠️ XAML Notes = | = ⚠️ XAML Notes = | ||
− | + | ||
− | * Due to a XAML Toolkit upgrade, the items at the bottom of the global sidebar appear clipped. At the same time, the NavigationView styling was streamlined in both UBIKThemes, and the content areas (UBIKContentArea, UBIKRootArea, UBIKDocumentArea, UBIKQueryArea). Already-existing customized versions of these pages will need to be adapted to see these changes. In rare cases, the Navigation View in already existing customized templates will appear broken (white background, reduced functionality) and require conversion. For | + | * ⚠️NavigationView: Due to a XAML Toolkit upgrade, the items at the bottom of the global sidebar appear clipped. At the same time, the NavigationView styling was streamlined in both UBIKThemes, and the content areas (UBIKContentArea, UBIKRootArea, UBIKDocumentArea, UBIKQueryArea). Already-existing customized versions of these pages will need to be adapted to see these changes. In rare cases, the Navigation View in already existing customized templates will appear broken (white background, reduced functionality) and require conversion. |
+ | {{Expander|indent=22px|heading=Steps to Conversion|content= | ||
+ | *<b>Step 1:</b> For each custom; UBIKContentArea, UBIKRootArea, UBIKDocumentArea, UBIKQueryArea: | ||
+ | ** Remove the <muxc:NavigationView ...> and inline notes. | ||
+ | ** Replace it with the ContentControl that references the new UBIKNavigationView as it's template found in any of the default area templates named above), and optionally the xaml notes, documented below. | ||
+ | <nowiki><!-- | ||
+ | From 4.4 The NavigationView has been restructured to require less xaml customizing. | ||
+ | A single template (UBIKNavigationView) is now defined in UBIKThemes, and referenced via ContentControl in UBIKRootArea, UBIKContentArea, UBIKQueryArea, UBIKDocumentArea. | ||
+ | The page content is now simply inserted as a child of the ContentControl. | ||
+ | --></nowiki> | ||
+ | <ContentControl Template="{StaticResource UBIKNavigationView}"> | ||
+ | Do not forget to also convert the closing tag at the end of the xaml. | ||
+ | |||
+ | *<b>Step 2:</b> Unfortunately, due to the way our themes are loaded, we need to include the new items in our custom UBIKThemes in order for customized color resources, like UBIKAccentColor, to be reflected on the NavigationView (otherwise it will always be standard orange). | ||
+ | ** We also need to remove the old customizing to prevent interference of these styles. | ||
+ | ** Clean up your UBIKThemes by removing all of the standard customizing from before the update. The easiest way is to; | ||
+ | *** Search in your custom UBIKThemes.xaml for the NavigationView section (you can find it between the tags: <!--#region NAVIGATION VIEW-->) and remove all the contents from this region. | ||
+ | *** Use Developer Mode to unpack or access the newest standard UBIKThemes, and paste in the two following items in their entirety (make sure you get the entire item, until its closing tag): | ||
+ | <Style x:Key="UBIKPaneToggleButtonStyle"...></Style> | ||
+ | <ControlTemplate x:Key="UBIKNavigationView">...</ControlTemplate> | ||
+ | }} | ||
+ | * More than 8-10 root items overflowed the navigational sidebar buttons in the updated NavigationView described above. The fix was applied to the UBIKGlobalSideBarButtons template for least chance of conflicting with a customized template. If your project has a customized version of this template and more than 8-10 items, please copy the Height attribute and VisualStateManager from the new default template. | ||
+ | * Invalid value indicator in [[Property_Direct_Edit_(Client)#ValueItem.PropertyValue_or_ValueItem.PropertyValueSessionless|property direct edit]] moved from UBIKPropertyDirectItemTextBox.xaml and UBIKPropertyDirectItemGeoData.xaml into UBIKPropertyDirectItemContainer.xaml to unify for all properties. | ||
+ | |||
<headertabs /> | <headertabs /> |
Latest revision as of 14:33, 4 September 2023
This version requires Windows 10 build 17763 or higher |
Availability
Store: Publicly available in Microsoft Store.
Store Beta: Publicly available in Microsoft Store as beta versions to those whose account email is included in our beta program. Please contact the Augmensys staff and submit your chosen email address if you would like to join.
App Center: Available to those who have access to the Augmensys App Center.