-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Animation Examples #406
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I notice in the animation example you are hiding the EasingsPage. On evaluation it appears to expose the dreaded "Layout cycle detected. Layout could not complete." which has never been confirmed as an issue even-though there a lots of issues that have been logged and closed.
Please can you confirm why this example has been excluded from the demo and if a fix is scheduled? While evaluating MAUI people will look for these code smells and try to question/report but when they don't follow up with a diagnostics, its likely that they have switched to another framework and incorrect to assume that the problem is fixed.
I want to give MAUI a chance as this would be my preferred framework... if I can get it to pass due diligence.
Reproduction steps:
Add an extra ShellContent to expose the hidden page to 8.0\Animations\Animations\AppShell.xaml:
<ShellContent Title="Easing" ContentTemplate="{DataTemplate local:EasingsPage}" Route="easing" />
Uncomment the following line in 8.0\Animations\Animations\Pages\Controls\EasingCard.cs:
await Shell.Current.GoToAsync($"{nameof(EasingEditorPage)}", navigationParameter);
Debug the demo on windows and navigate to the Easing demo
Double click on an EasingCard to get the UnhandledException:
{Microsoft.UI.Xaml.UnhandledExceptionEventArgs} Exception: {"The text associated with this error code could not be found.\r\n\r\nLayout cycle detected. Layout could not complete."} Handled: false Message: "Layout cycle detected. Layout could not complete."
The text was updated successfully, but these errors were encountered: