Suggested plan for the next version 2.x #5250
Replies: 34 comments 107 replies
|
As I have said elsewhere, Windows App SDK is no good for business applications until such time as there is a working UI validation framework. Personally, I am happy with the interfaces available in WPF (though many on here disagree with me and feel something better could/should be provided) - especially as it would make for easier reuse of existing back-end code - but at least give us something. |
|
Yes, I sometimes use WPF, but I hope WinUI can achieve what it deserves. |
|
And I have said elsewhere, but I will repeat here, not being able to bind numberboxes to decimal (currency) values is about just as bad for business applications as not having validation. Anyone who works with currency values knows to use decimal to store them in SQL Server or other DB and in C#. When you bind numberboxes to decimal indirectly using a double-to-decimal and vice-versa conversion, you run the risk of rounding issues, making it near impossible for us to continue with our business application appropriately. I don't know what to do but BEG someone to fix this. WinUI is great, but this and some of the other issues above really are preventing mass adoption and it is such a shame. |
|
Hi, Howard Kapustein (@DrusTheAxe) Roy (@RDMacLachlan) WASDK v1.8-preview has been released, but it looks like the Decimal feature (Microsoft.Windows.Foundation namespace) isn’t available. Is it planned for the v1.8 stable release? and when will we be able to access it? |
Doh! I found it - a bug in the build process created Microsoft.Windows.Foundation.winmd but didn't get into the nuget+msix packages. Fix going up shortly. Thanks for bringing this to our attention! |
|
Howard Kapustein (@DrusTheAxe) Will that make it so I can finally do: |
|
Fix is up |
If you have a control and want to use the decimal support (DecimalValue and DecimalHelper), then yes :-) |
|
I love that you listed Kiosk Mode. I appreciate it. |
|
missing drag& drop support elevated ,@https://github.com/microsoft/microsoft-ui-xaml/issues/7690 |
|
..…and a better drag&drop handling, too. |
|
done |
|
Unfortunately, I believe this is a lost cause (Windows limitation). It already doesn't work for packaged Win32 apps, let alone Windows App SDK ones. |
I believe the problem lies in the direction and the decisions made. Computers are tools to assist people in their work. To sacrifice convenient functions for the sake of security is extremism. |
|
Please include fixing this issue in v1.8 too. It prevents the WinUI3 apps from being used in Hyper-V VMs and some other remote desktop scenarios because it causes a lot UI freezing. |
|
done |
|
Ty 🙏 |
|
Mahdi Hosseini (@ghost1372) it's not just related to VMs, here is another issue where I linked similar ones already reported. |
|
it might also be related to this one, which should arrive in 1.7, according to Mike Crider (@codendone) |
|
Bogdan Pătrăucean (@bogdan-patraucean) i added your issues to list |
|
I hope they look at numberboxes in general. There's so many problems with them.
I could list more issues with numberboxes but just searching this repo will list a lot more. |
|
Wow, NumberBox is even worse than I realized so far. I got stuck in our app with it not supporting decimal, I didn't even notice half of these problems yet. What a mess. |
|
And NumberBox displays 1e15 as 1000000000000000 only. |
|
Pin to taskbar is very unlikely to happen. Microsoft has pretty vocally stated that they do not want such an interface: https://devblogs.microsoft.com/oldnewthing/20141230-00/?p=43273 |
|
Pinning is currently possible for packaged apps. While Microsoft has restricted it to unpackaged applications, there is a way to get around it. It is now possible to pin any app with c# and unpackaged mode. But why not create a standard way? Must definitely be revised in decisions |
|
Read the article. |
|
Isn't this exactly done like theoldnewthing describes by driving the context menu? Just because something can be done does not mean it should be done. |
Worth to read: https://geelaw.blog/entries/msedge-pins/ |
Feature should also include xaml 2009 in .net |
|
tnx, i added microsoft/microsoft-ui-xaml#7037 to list |
|
Before requesting anything, i want to thanks the WASDK team for their hard work and effort, i understand it's hard for you to manage the project with few team members and i dearly hope MS will give you more funds and human resources I want to request making the Window control inherit from DependencyObject this will make extending and fixing bugs much easier, like creating a BaseWindow class the inherit from DependencyObject and combines it with the current window control functionalities then making the window control inherit from BaseWindow might leads to more benefits and improvements Thanks for reading my post, i appreciate WinUI 3 and WASDK and their team |
|
Thanks for the WinUI team for the continued efforts. WinUI has been continuously neglected by MS and I'm glad to see it's being worked on. |
|
Roy (@RDMacLachlan) Mike Crider (@codendone) is anyone in the team actually reading these posts (or this one)? |
|
Hi everyone, |
Roy (@RDMacLachlan) has just restored my faith in humanity. |
|
Hi Roy (@RDMacLachlan) |
|
This thread and the 1.7 release thread show that there are still people that want to move the platform forward. Please don't continue as the previous releases where the community around WinAppSDK was mostly ignored. |
|
Yes, fortunately it has been merged. |
|
A C#/WinRT rewrite? Can you give me a link talking about that? I'm interested |
https://github.com/microsoft/CsWinRT/tree/fhl/cswinrt-3.0/src/WinRT.Runtime2 |
|
Thanks |
|
I think if xbind is implemented for the ResourceDictionary (No Code-Behind), most of the AoT problems for custom controls will be solved. |
|
Thank you, I added it. |
|
高怡飞 (@Gaoyifei1011) You reposted the long, original post eight times in your responses. Please try to not do that 😉 |
Thanks for your advice.I will notice that.😂😂😂 |
I have been mergeded it and remove duplicated comments. |
|
I would love to see SVG compatibility throughout. DevExpress fully supported them in all their controls in WinForms, allowing our apps to look their best at all resolutions and scaling. It feels like a big step backwards in WinUI not being able to use SVG images everywhere that scale properly. |
|
Agree, see microsoft/microsoft-ui-xaml#1494 for all the problems with icons. |
Hahah, I actually made the last post in that thread when I first started with WinUI and saw what a mess icons were. I forgot about it. |
|
added to list |
|
It's a bit late, but I'd like to highlight my pain points during development:
Generally, the controls can be more friendly for data binding. |
|
Mahdi Hosseini (@ghost1372) can you please review this? I haven't seen any reaction. |
|
Hi Huo Yaoyuan (@huoyaoyuan) |
Where is Xaml2018? When will we enter the official version of the Windows App SDK (WinUI 3)? --------------------------------Xaml2018在哪里？什么时候进入到 Windows App SDK（WinUI 3）的正式版？
|
|
tnx, added to list |
idisplayinformation2 api 与 oriention 和 dpi 相关，但是该api长期是实验性api，所以我希望能把这个改进加入。什么时候在正式版中提供相关api及其功能? The idisplayinformation2 API is related to orientation and DPI, but this API has long been an experimental one. Therefore, I hope this improvement can be included. When will the relevant API and its functions be provided in the official version? |
|
added to list |
|
I just raised an Issue related to experimental apis. Some experimental apis have remained in the preview version for several years since their birth and have not been officially recognized. So here I hope to add them to the to-do list so that MS can reconsider these experimental apis and remove the experimental labels in a timely manner for use in the official version --------------------------------------我刚才提了一个 Issue 是有关实验性 API 的，部分实验性 API 自从诞生起到现在经历了好几年就一直停留在预览版中，没有转正。所以在这里我希望能加到待办列表中，让 MS 能重新考虑一下这些实验性 API，并能及时移除实验标签，在正式版中使用 |
|
The development team, and I discussed your issue yesterday. We converted it into a discussion to invite broader community feedback. Thank you for highlighting it as something you would like to see happen. |
|
Mahdi Hosseini (@ghost1372) , we also need support for elevated apps to be able to show toast notifications. Right now the docs are stating that:
I have a use case for this: if my app silently fails I want to display a toast with the issue so people don't have to guess what happens and why the app does not launch. |
|
Added to list |
|
Game pad APIs are just windows APIs. Here’s some example code I wrote to navigate a 3D view: https://github.com/Esri/arcgis-maps-sdk-dotnet-demos/blob/main/src/KmlViewer/XInputHelper/XInputSceneController.cs |
|
Suggestion for discussion title: Suggested plan for the next version 1.9Microsoft has become obsessed with updating AI-related features, neglecting a large number of basic feature requests and bug fixes. This is really unfortunate. |
So, where on earth is the WinUI 3 XAML Designer? Microsoft, please tell me. |
|
thank you |
|
`` |
Based on the commit records of the wasdk branch, the next version might skip 1.9 and directly go to 2.0, as there is a 2.0/release branch. |
|
is there any specific reason? |
https://github.com/microsoft/WindowsAppSDK/tree/release/2.0-stable You can take a look at this branch. It emerged after the release of the 1.8 official version. Every time wasdk releases a new official version, a new branch corresponding to the next version will be created. Personally, I don't think this is groundless. I guess it might be related to cswinrt3.0, after all, cswinrt3.0 is a version with significant changes. |
|
Is this the actual plan for wasdk or are they just doing minor bug fixes with AI features no one asked for? |
|
Microsoft, please do not ignore the requests of developers. |
|
This should be a priority, please triage this. |
|
Files suffers from this and I think many us suffer from this missing. |
|
on ultra-wide monitors this is insane. makes the apps look really bad and not well written which is generally not the case. |
|
there is an experimental api, but never shipped into stable releases |
|
Yes, it was requested in 2020, and last year it hit experimental. But not shipped - so it doesn't exist ! No one is going to use experimental in code, and if they do, the store review process can reject those submissions. So ther request is still valid, please prioritise this basic window feature that users expect. |
|
It's really sad to see how few issues from here were addressed so far. Instead we get more and more AI APIs we can not even opt out of properly because of broken dependencies between WinAppSDK and the CommunityToolkit which still includes WinAppSDK 1.6. The previews now depend on >=WinAppSDK1.8 which fixes this but if you also use anything from CommunityToolkit.Labs then you're still stuck. I currently delete the AI libraries and winmd files using post build actions but this is not how it should work... |
|
AIs are optional, i only use these and that's all I need for WinUI3 |
|
They are not optional if you include any package that still depends on WinAppSDK 1.6 like CommunityToolkit and CommunityToolkit.Labs. Did you read the post until the end? Any package that includes WinAppSDK 1.6 or well any version below 1.8 will transitively add this dependency to your project if you only depend on the meta packages and cause an error on build. See this for example: CommunityToolkit/Windows#825 (comment) When the next version of the CommunityToolkit releases, this will be fixed but there's more packages having the same issue. Like CommunityToolkit.Labs |
The list is stale. This was added in 2.2.0 |
|
Thank you, Howard Kapustein (@DrusTheAxe) I've removed it from the first post. What you're seeing is from the quoted/replied message. |
and others
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
These are things we need and have been asking for years but have never been considered.
I hope Microsoft will consider this list. Also, if nothing is going to happen to any of the items, we expect a proper explanation so that we don't have to waste our time waiting to deal with it.
Instead of working on trivial things, focus on the following:
Controls
Features/APIs
Non-XAML ThemeResourcemicrosoft/microsoft-ui-xaml#10029(microsoft/microsoft-ui-xaml#11229)Bug Fix
TitleBar Bug Fix
All reactions