-
Notifications
You must be signed in to change notification settings - Fork 667
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
Proposal: Support DependencyPropertyKey and RegisterReadOnly as in WPF #3139
Comments
@MikeHillberg Can you help me understand the tradeoff between RegisterReadOnly versus a OneWay binding? Is the value here that you can't do a TwoWay binding because it's captured by the DependencyProperty itself? |
You can't do a TwoWay binding, nor set it from a Style Setter or VisualState, nor can you call the property setter explicitly from code. Without this feature you can still simply not have a property setter, but that doesn't affect the mechanisms that set the DP directly. |
This is needed for controls and library authors mostly I believe. For instance the WPF docs site an |
Needed |
Proposal: Support DependencyPropertyKey and RegisterReadOnly as in WPF
Summary
Support is needed for read-only dependencies properties in UWP/WinUI. This is especially true for collection-type properties backed by a list that shouldn't be changed through the binding system. It will also allow several existing properties to be updated to support binding and MVVM (which is important in several application-specific scenarios).
Rationale
This is needed several places (examples listed below) and has been a rather large architectural gap since UWP inception as compared to WPF.
Scope
Important Notes
Switching to using read-only DPs in existing controls would be a binary breaking change but as the property accessors could be the same it would be minor. It would just enable binding.
Also see the discussions here:
The text was updated successfully, but these errors were encountered: