Hi,
We have a Maui app that uses a SfRotator that loads the templates from xaml files.
I have tested with the latest version of the Nuget packages v27.2.2 and noticed that the templates do not load at all. They were previously workin in v27.1.57 which is the current version we are using with out app. This happens on Windows and Android with v27.2.2.
I have made a sample app for you that uses the templates. It has the latest version 27.2.2. You will see that the templates dont load at all.
I have also noticed some bugs in v27.1.57 with the rendering of controls in the rotator. However I cant test these in the latest version as the rotator doesnt load.
1.The combo box doesnt show options inside of the rotator. However it does work inside of Page2 in the menu.
2. If you also look at template 3 in the rotator you will notice that the syncfusion controls do not render properly.
You can see on Android what it is meant to look like.
Attachment: Both_Sample_Apps_8acf077d.zip
Hi Mark,
Query 1: In the latest version of the Nuget packages v27.2.2 and noticed that the templates do not load at all
We have reviewed your query and successfully reproduced the reported issue on our end. The issue has been resolved, and the fix will be included in our upcoming weekly release scheduled for November 21, 2024. We will notify you as soon as the NuGet package is released. We appreciate your understanding and patience in the meantime.
Query 2: The combo
box doesnt show options inside of the rotator. However it does work inside of
Page2 in the menu.
We have reproduced the reported issue. The issue occurs when the IsEditable
property of the SfComboBox is set to false; it works as expected when
IsEditable is set to true. We are currently investigating this issue and will
provide further details by November 22, 2024.
Query 3: If you also
look at template 3 in the rotator you will notice that the syncfusion controls
do not render properly.
To resolve the reported issue, we made some modifications to your sample. To
render Syncfusion controls at runtime, you need to call the Refresh method of
the SfRotator in the respective ViewModel class. In the attached sample, we
invoke the Refresh method in the ViewModel by passing the Template3View page as
a parameter to the button command. In the Template3ViewModel, you can cast the
parameter to access the SfRotator and call its Refresh method. Please refer to
the attached sample for details.
|
<button:SfButton Text="Add a Once Off Withdrawal" IsVisible="{Binding HideAddAdHocWithdrawalButton, Converter={StaticResource InvertedBoolConverter}}" Style="{StaticResource MediumButtonStyle}" Command="{Binding AddAdHocWithdrawalCommand}" CommandParameter="{x:Reference Template3ViewXaml }"/>
private void ExecuteAddAdHocWithdrawalCommand(object parameter) { SetupAdHocWithdrawal(); HideAddAdHocWithdrawalButton = true; (((parameter as StackLayout).Parent as ContentPresenter).Parent as SfRotator).Refresh(); } |
Please let us know if this solution addresses your issue. If you have any further questions or concerns, don't hesitate to reach out to us.
Regards,
Aarthi A.
Hi Mark,
Query 1: In the latest version of the Nuget packages v27.2.2 and noticed that the templates do not load at all
We have included a fix for the reported issue, "Rotator does not update templates in Android and Windows" in our latest weekly NuGet release, v27.2.3, which is now available for download (NuGet).
We thank you for your support and appreciate your patience in waiting for this update. Please get in touch with us if you would require any further assistance.
Query 2: The combo
box doesnt show options inside of the rotator. However it does work inside of
Page2 in the menu.
Thank you for your patience. We attempted to address the reported issue where
setting the SfComboBox as the ItemTemplate of SfRotator triggers the Unfocus
event immediately after the Focus event when tapping the DropDownIcon in
SfComboBox. We are currently investigating this behavior and explore possible
solutions. We will share our findings and an update on or before November 26, 2024. We appreciate your
understanding and patience during this time.
Regards,
Aarthi A.
Hi Aarthi,
Thank you very much for the fix for the Rotator. I can confirm it works on my side.
I will test the combobox once you get back to me.
Thanks,
Mark
Hi Mark,
Thank you for your patience. We would like to inform you that the SfRotator control is designed primarily for displaying items and is not the most efficient choice for your use case. Instead, we recommend using SfTabView, which allows you to swipe through items and handle touch-related actions more efficiently.
In your sample, we made the following modifications:
By switching to SfTabView, you can resolve the reported issues, such as loading Syncfusion controls correctly and displaying options in SfComboBox.
We have attached the modified sample and included code snippets below for your reference. Please review them for further details.
|
<DataTemplate x:Key="WizardItemTemplate"> <ContentView Content="{Binding Template}" /> </DataTemplate>
<sf:SfTabView EnableSwiping="True" ItemsSource="{Binding WizardTemplates, Mode=TwoWay}" ContentItemTemplate="{StaticResource WizardItemTemplate}" SelectedIndex="{Binding WizardIndex, Mode=TwoWay}" TabBarHeight="0" VerticalOptions="FillAndExpand"> <sf:SfTabView.Behaviors> <behaviors:EventToCommandBehavior EventName="SelectionChanged" EventArgsConverter="{StaticResource SelectedIndexChangedConverter}" Command="{Binding WizardSelectedIndexChangedCommand}" /> </sf:SfTabView.Behaviors> </sf:SfTabView>
|
Please let us know whether the provided suggestion helps to resolve your query. Please don’t hesitate to contact us if you have any concerns or queries.
Regards,
Aarthi A.
Hi,
Thank you for your response. We will investigate using the tab control instead of the rotator. This does unfortunately mean a big delay in our project. If it solves the problems we have been having it will be worth it.
Thanks very much for your help so far, your support is excellent.
Thanks
Mark.
Hi Mark,
You're welcome. Please check the provided sample and get back to us. We will await your response.
Regards,
Preethi R