Alex-Dobrynin
commented
1 year ago It seems to me that this is the end for Microsoft's mobile team. They do not fix own bugs, they do not respond to the tickets, the even do not review PRs made a year ago to fix BASIC feature of MVVM - Bindings. All they do is blah blah blah to the camera. Poor, very poor management. When i firstly heard about maui, it was said that it will be revolution in .net mobile development. I thought it will be some kind of XPF (x-platform WPF), the render engine will be based on skia and we will be able to style everything and everywhere, like it is in WPF and we will never do ui based platform-specific things, like it is in Flutter. But what do we have? Very laggy buggy 'XF', and if you need some not standard implementation of controls maui provides you, you need go and implement platfrom-specific things. Even XF has better performance and less bugs. They could go and look how avalonia managed to implement this, but no, they trying wrap shit into a candy wrapper. IMHO
foximoxi
Description
DO NOT CLOSE THIS ISSUE BECAUSE YOU THINK IT DOEN'T MEET THE CRITERIA OF A VALID ISSUE! THERE ARE SOME VERY SALIENT ISSUES BEING RAISED IN THIS ISSUE.....
I have reported issues as far back as Feb, 2022, and of as now, many of these reported issues remain unfixed. This is really a poor situation where I have to open an issue to complain about issues not being fixed. The lack of response to issues IS the issue.
I reported an issue (#4672) and here we are at .NET 8 and this VERY BASIC thing remains unfixed. @davidortinau I know I have been critical of the lack of desktop support and I do applaud your efforts in shoring up this deficiency in the latest releases, but how long do we have to wait for the most basic MAUI stuff to work properly?
When I open a window that has frames, it almost NEVER draws correctly. You have to resize the window to force a layout recalculation for things to correct themselves. Here is a picture of an app that has a flyout strip and it never draws correctly until a window resizes:
You can see that the button row is not centered. Here is the same screen after a window resize.
I reported this almost 2 years ago and you (David) even added comments to the original issue: Controls/Layout does not draw controls correctly in first-time view. #4672
It has been in the backlog ever since and I would think that something that makes a MAUI app look like total s&#t would be a concern of the MAUI team.
Also, I reported the fact that easy controls like Switch cannot have its basic colors changed (at least at the time I reported the issue: There is no way to set the text color of a Switch control #8965). Gerold V just took it upon himself to close my issue by telling me, in essence, we are not going to do stuff like this. I should go write platform-specific code. That's ridiculous because what is platform-specific about the Switch control??? In WPF EVERYTHING was stylable... Why is it the responsibility of the development community to do your work by writing handlers and such to get something simple to work?
Also, take a look at the screenshots above. Notice the minimize, maximize, and close buttons are double-drawn. How does this stuff pass QA??????
I am getting ready to roll this out to 2000 perspective users and I will not be proud of 99.99999% of the app because of the visual aspects of MAUI. I looked at UNO and Avalon back when I was deciding to go cross-platform and I decided to stick with Microsoft all the way for everything: .NET, MAUI, gRPC, ASPNETCORE, etc... I wanted the whole stack to be Microsoft, but I am ruing my decision... MAUI is great in concept, but not in implementation. Simply upgrading Xamarin to MAUI did not buy the community much in the whole product delivery. You guys have focused far too much effort on sapping milliseconds out of performance while glaring visual bugs persist. I think 90% of the attention should be placed on fixing bugs and performing better QA. I know stuff breaks from release to release and I would think that decent regression testing would catch stuff like this. I also think you guys need to look at WPF and figure out how to achieve the functionality that existed there before developing new stuff. I would love a WYSIWIG XAML editor so we can see what we are designing without having to run the app. This brings me to Hot Reload which RARELY works! It does work on straight XAML, but not XAML in templates. I see it work there, but as I said, rarely.
I have been a developer since 1984 and have focused much of my career on UI design. WinForms was great and WPF was even greater. MAUI isn't even making the charts... I sometimes spend hours trying to get something that was easy in WPF to work in MAUI and that is time I don't have...
Yes, this rant is probably misplaced here in the issues log, but how else can somebody truly vent their frustrations about developing with MAUI? I spoke via a TEAMS meeting early last year with both David and Maddy and I let my opinions be known then. Here it is almost two years later, and nothing is even slightly easier to develop in MAUI... I would love for David to be made aware of this "issue" and have him contact me directly. This doesn't even scratch the surface of my frustrations...
I really want to talk to @davidortinau directly. Please pass this on to him.
Regards, Steve Miller
Steps to Reproduce
No response
Link to public reproduction project repository
No response
Version with bug
8.0.3
Is this a regression from previous behavior?
No, this is something new
Last version that worked well
Unknown/Other
Affected platforms
Windows
Affected platform versions
No response
Did you find any workaround?
No response
Relevant log output
No response