Replies: 1 comment 4 replies
-
Microsoft.UI.XAML is WinUI 3 Windows.UI.XAML is UWP (WinUI 2) IMO reveal, tilt, and liberal use of acrylic were just implemented to show off the composition engine. Using any of them on a regular basis just turns into a distraction and detracts from productivity. New rounded corners get a 'meh' from me - at least there isn't a notch somewhere. The new tabs are a mess at the moment. Not sure how much is attributable to bugs vs. design decisions. |
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Why weren't the styles just taken from UWP?
Maybe this is a personal thing, but to me the new styles just look way worse than whats in Microsoft.UI.Xaml.
Please share your experiences.
Sample 1 - NavigationView
In UWP you can see the hovered item and the large underline clearly shows the current active item. Its dense, compact and crisp. The WinUI version does NOT show the hovered item. While you can't see the mouse cursor on the picture, i assure you that i hovered it while taking the screenshot. The small dotlike outline is hard to see.
UWP:
WinUI3:
Sample 2 - TabView
I don't think there is much to say about the UWP version, maybe that the vertical spacer is on top of the tab header. Otherwise it looks clear and well defined to me. I am speechless at how bad the WinUI3 version looks. I have not seen such a bad looking TabControl since owner drawn Windows XP tab controls. The button like selected tab doesn't even look like it belongs there. To me it looks like something glitched the rendering. The visual difference of the color between selected and hovered is so minimal that it is hard to tell which is which.
UWP:
WinUI3:
Beta Was this translation helpful? Give feedback.
All reactions