Browse Source
If we have e.g. a named UserControl in a window then we want that control to be findable by name from the Window, so register with both name scopes. This differs from WPF's behavior in that XAML manually registers controls with name scopes based on the XAML file in which the name attribute appears, but we're trying to avoid XAML magic in Avalonia in order to made code-created UIs easy. This will cause problems if a UserControl declares a name in its XAML and that control is included multiple times in a parent control (as the name will be duplicated), however at the moment I'm fine with saying "don't do that". Fixes #829.pull/843/head
3 changed files with 66 additions and 0 deletions
Loading…
Reference in new issue