-
Notifications
You must be signed in to change notification settings - Fork 78
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
Implement styles for all Avalonia's controls #234
Comments
Could you elaborate on how to use Right now I'm trying to get a When I place fluent first, like so:
I get:
When I place it last or in its own Selector (just for the How can I set it only for that specific control (or as a fall back if there's no material style for a control?) (Btw, looking at fluent again after only working with this material for a while now, makes me really appreciate your work all over again! Beautiful design!) |
Hello, @NoizeDaemon. Thanks for the kind words) As about your problem, i can just do this at my example project: <Application.Styles>
<FluentTheme />
<themes:MaterialTheme />
... And everything works fine. Can you provide a minimum representable example with your error, please? |
Here is the sample: https://github.com/NoizeDaemon/MS It runs without When putting When putting Edit: |
@NoizeDaemon, I've commented a Calendar styles (they need a bit more polishing) and it works fine with latest nightly. Give it a try. |
Works now! :) Thank you! |
Add styles for RefreshContainer, RefreshVisualizer, PathIcon, CaptionButtons, TitleBar #234
Since we positioning
Material.Avalonia
as standalone styles library we should add styles to all existing Avalonia controls.Of course anyone can just reference
FluentTheme
before our theme and withControlThemes
it will work fine, but we should provide a basic support for all controls.List of currently missing controls:
TitleBar
to support close/maximize buttons when ExtendClientAreaToDecorationsHint=True #246New files should be created in
Resources/Themes
folder and imported inMaterialToolKit.xaml
.All PRs and support are highly appreciated.
The text was updated successfully, but these errors were encountered: