Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Control Styles should be named
See original GitHub issueWhile investigating this, I noticed an issue for this that is a complete show stopper: there is no way to override the default TabViewItem style. Unlike some other controls, the TabViewItem does not follow the pattern of:
<Style TargetType="ControlName" BasedOn="DefaultControlNameStyle"/>
<Style x:Key="DefaultControlNameStyle" TargetType="ControlName">
...
</Style>
but rather just exposes the complete template as the default style leaving users with no choice of easily overriding the default style. However that is something that we would need for this feature to be easily usable. @ranjeshj @stmoy @StephenLPeters Is that something we can change to make that customization easier?
@michael-hawker FYI
_Originally posted by @chingucoding in https://github.com/microsoft/microsoft-ui-xaml/issues/2587#issuecomment-732463534_
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:14 (9 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Default[Control name]Style seems like the best approach, and should be used for all controls that present UI.
It also allows for Variations like “AccentButtonStyle” or “GhostButtonStyle” in the future.
Looking at the Win10 SDK generic.xaml, the pattern seems to be to not have named default styles at all. In the WinUI repo, the “Default[Control name]Style” pattern has been used a lot.