-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Switch SplitView.IsPaneOpen to a StyledProperty #10138
Conversation
Includes other small formatting changes and updates
You can test this PR using the following package version. |
@amwx For the PaneClosing event you made it a CLR (non-routed) event. I'm assuming that was for API compatibility with UWP. You also copied over the SplitViewPaneClosingEventArgs which supports cancellation instead of using CancelEventArgs already built-in to .NET. @tomenscape In your StyledProperty branch you switched this control to using routed events and this would switch to CancelRoutedEventArgs (a breaking change). And also support cancellation in opening. Is everyone OK with using @tomenscape approach? This standardizes with Expander:
|
You can test this PR using the following package version. |
You can test this PR using the following package version. |
These breaking changes don't seem critical and are quite easy to fix in the user code. Keeping in mind we are in preview stage still. |
You can test this PR using the following package version. |
You can test this PR using the following package version. |
What does the pull request do?
Switches the SplitView.IsPaneOpen property to a StyledProperty. This follows the Expander control changes (SplitView was originally based on Expander for this property #9944 (comment)).
cc @amwx (original author)
What is the current behavior?
IsPaneOpen is a DirectProperty and cannot be styled.
What is the updated/expected behavior with this PR?
How was the solution implemented (if it's not obvious)?
See code.
Checklist
[ ] Added unit tests (if possible)?[ ] Added XML documentation to any related classes?[ ] Consider submitting a PR to https://github.com/AvaloniaUI/Documentation with user documentationBreaking changes
Yes
Obsoletions / Deprecations
None
Fixed issues
Fixes #9800
Part of #9944