Difference between revisions of "Version 4.4 (WinX)"
(Templated the Expander :)) |
|||
| Line 75: | Line 75: | ||
* ⚠️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. | * ⚠️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. | |
| − | <b>Step 1:</b> For each custom; UBIKContentArea, UBIKRootArea, UBIKDocumentArea, UBIKQueryArea: | + | <nowiki><!-- |
| − | Remove the <muxc:NavigationView ...> and inline notes. | + | From 4.4 The NavigationView has been restructured to require less xaml customizing. |
| − | Replace it with the ContentControl that references the new UBIKNavigationView as it's template | + | 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. | 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). | + | *<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. | + | ** 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; | + | ** 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. | + | *** 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): | + | *** 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> | |
| − | <Style x:Key="UBIKPaneToggleButtonStyle"...></Style> | + | <ControlTemplate x:Key="UBIKNavigationView">...</ControlTemplate> |
| − | + | }} | |
| − | <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. | * 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. | * 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. | ||
Revision as of 12:25, 26 July 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.
| Some customized XAMLs might need an update to work properly. These changes are marked with ⚠️ |
