-
Notifications
You must be signed in to change notification settings - Fork 730
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
UserControl fixes #3279
UserControl fixes #3279
Conversation
559542c
to
5c7e86a
Compare
5c7e86a
to
1a95506
Compare
src/SourceGenerators/Uno.UI.SourceGenerators/XamlGenerator/XamlCodeGeneration.cs
Show resolved
Hide resolved
1a95506
to
6359cf2
Compare
The build 15952 found UI Test snapshots differences.
|
The build 15958 found UI Test snapshots differences.
|
The build 15958 found UI Test snapshots differences.
|
The build 15958 found UI Test snapshots differences.
|
…lf, not the first child Fixes #3243
BREAKING CHANGE: This update now forces the materialization of UserControl instances in the visual tree. - UserControl no longer incorrectly accepts VisualStateManager, and must be placed on the first child - To restore the skipping of UserControl instances, add the following in the csproj: ```xml <UnoSkipUserControlsInVisualTree>true</UnoSkipUserControlsInVisualTree> ``` Fixes #61
6359cf2
to
481f20c
Compare
...ts/Windows_UI_XAML_Controls/UserControlTests/UserControl_TopLevelBinding_UserControl.xaml.cs
Show resolved
Hide resolved
|
||
public static void SetMyProperty(DependencyObject obj, int value) | ||
{ | ||
obj.SetValue(MyPropertyProperty, value); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The build 15995 found UI Test snapshots differences.
|
GitHub Issue (If applicable): Fixes #3243, Fixes #61, Fixes #3218, Fixes #153
PR Type
What kind of change does this PR introduce?
What is the new behavior?
UserControl
instances are now placed in the visual tree by default.PR Checklist
Please check if your PR fulfills the following requirements:
Screenshots Compare Test Run
results.Contains NO breaking changesOther information
Internal Issue (If applicable):