-
Notifications
You must be signed in to change notification settings - Fork 706
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
TabView: Fixed many things #1158
Conversation
@@ -420,8 +431,9 @@ | |||
MaxWidth="{ThemeResource TabViewItemHeaderIconSize}" | |||
MaxHeight="{ThemeResource TabViewItemHeaderIconSize}" | |||
Margin="{ThemeResource TabViewItemHeaderIconMargin}"> | |||
<ContentPresenter x:Name="Icon" | |||
Content="{TemplateBinding Icon}" | |||
<ContentControl x:Name="IconControl" |
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.
Something like this would be useful just in general, in terms of a control that you can give an IconSource and it'll put the resulting IconElement into the UI tree. I imagine that, given that this has already gone through API review, now wouldn't be the time to address that, but we should file an issue if we don't already have one saying that we should make a control like that. I don't imagine it'd be a big work item, and it'd be a handy utility. We had one of those in the OS repo, but it was pulled prior to 19H1 due to not having gone through API review in time.
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.
Jevan actually started a thread about this, so I'll await the results -- but agreed, it's not very attractive as is.
|
||
[WUXC_VERSION_PREVIEW] | ||
[webhosthidden] | ||
unsealed runtimeclass TabViewItemTemplateSettings : Windows.UI.Xaml.DependencyObject |
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.
Just to make sure, this was also put through API review, right? I found out the last time I added a template settings class that they also need to go through API review despite being ultimately just an implementation detail, so I wanted to make sure.
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.
Well... no, admittedly. I didn't know it needed to. I'll email Mike about it then.
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.
Glad I asked, then. :) I didn't know these needed to go through API review either.
I'll do that in the next commit when I actually change all the names to the API reviewed ones. |
…will follow up and look into it later this week. Disabling for now.
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.
🎉 Handy links: |
One test is currently failing -- need Keith's help with that tomorrow.