Replies: 27 comments 69 replies
-
Are there any improvements to Xaml coming soon, It's been years since Xaml saw substantial improvement in WinUI/UWP Space. As you can see in Maui Xaml it evolved to a place where we can do many things easily without much hassle like we have on WinUI. I.e Binding Extension and etc.. |
Beta Was this translation helpful? Give feedback.
-
Just for kicks, collecting all the links where people have asked Microsoft to implement a XAML designer/previewer, and Microsoft has continuously ignored the community: Xamarin Forms: .NET Maui: WinUI 3: Visual Studio Developer Community: I'm sure I missed a lot. Those are the ones I could readily find. So many requests by community members for a designer. And so much silence from Microsoft. |
Beta Was this translation helpful? Give feedback.
-
It would be great if the team would address how they plan to improve how this project is being handled. We're years in at this point, there is still no Win UI 3 source available - perhaps the community can get bugs fixed and all the trivial things which seems to be too hard to get done? Further, the purge of 2.5k or whatever it was issues under the guise of "the team will now start triaging issues"... hasn't happened. There are pages of issues with no input from anyone working on this project. Is the team planning to start actively working on the backlog? It feels like development of Win UI has pretty much stopped. What little work that is done is always chasing the shiny new thing with no effort to fix long standing bugs and limitations (there are many). I'm pretty passionate about this platform but as I discussed here it appears that it's directionless. That may very well not be the case but I'm not the only person who holds that view. I'd also like some transparency as to how many people (FTE) are working on WinUI and how many FTE are developers. |
Beta Was this translation helpful? Give feedback.
-
What is being done to improve performance of WinUI?
|
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
When can we publish the app as a PublishSingleFile? I have been waiting since version 1.0 was released! |
Beta Was this translation helpful? Give feedback.
-
It is more than 5 months, since Windows App SDK version 1.3 has been released and since that day we are reporting, that PasswordBox is not working properly for touch displays. All information has been provided for reproduction of bug but still nothing. Everybody ignores this, but this is important for, i think, almost every app, which is used on touch display, because almost everywhere you have to be today signed in. In my case, this is release blocker, because customers could not sign in to their systems.
Issue: #6291 |
Beta Was this translation helpful? Give feedback.
-
Please take a look at bug report #8832 |
Beta Was this translation helpful? Give feedback.
-
The position of WinUI on the development landscape is still very uncertain in regard to Microsoft's approach to the new versions of their major products. Teams is a web app. The new Outlook is a web app, too. Both are sluggish, the UX doesn't match anything of Windows and Fluent, and the new Outlook is so bad that I don't even want to get started about it. Integration of Web apps with the Shell and the rest of the OS is sub-par and is going to stay like this for long. Try drag and drop from a web app to Explorer and enjoy the results. On one of the calls it was said that Microsoft are so big that departments like Teams and Office are like companies within the company. Still, this is a weak excuse for the lack of vision over UI / UX and platform. Worse, Office has been a huge department for long, but it also contributed a lot to Windows: rich edit, ribbon, to name a few. Now, WinUI looks like a garage project within Microsoft. We need reassurance. A good one. Not vague and lofty comments, but good proof of the company's vision. |
Beta Was this translation helpful? Give feedback.
-
We (Xelion) have invested heavily in WinUI/WindowsAppSDK, and I get fewer and fewer stability related issues from our customers. I'd rather see these random XAML-related issues disappear. :) |
Beta Was this translation helpful? Give feedback.
-
Will we ever get a BlazorWebView for WinUI 3? There are so many reasons why a BlazorWebView should be available asap. Request dotnet/maui#7380 |
Beta Was this translation helpful? Give feedback.
-
It would be great to hear details of how the initiative closing old issues went and the benefits it has brought to the team/project. :) |
Beta Was this translation helpful? Give feedback.
-
I just wanted to say thanks for all that you all do. I’m sure you don’t hear it enough. 😁 |
Beta Was this translation helpful? Give feedback.
-
Any work planned on win2d? Looks like it is abandoned currently. It is currently the only managed interface to DWriteCore without building C++ wrappers. |
Beta Was this translation helpful? Give feedback.
-
You can use Direct2D in C# (like the last test sample with sprites I posted using SwapChainPanel) |
Beta Was this translation helpful? Give feedback.
-
Question about the new <Grid>
<SwapChainPanel/>
<ScrollViewer>
<StackPanel Width="..." Height="..."/>
</ScrollViewer>
</Grid> You could listen to the |
Beta Was this translation helpful? Give feedback.
-
I'm using WinUI 3 to build an app that uses multiple different user controls that utilize Direct3D to draw content. This is enabled by the fact that WinUI 3 provides the Unfortunately, bug #7924 was introduced after release 1.1 and to this day it prevents me from upgrading to any release after 1.1. It's not the first time I'm pointing this out in a community call discussion and there has been some progress but it is not yet fully resolved. I provided a full reproduction sample and I'm still hoping that someone squashes that bug soon. Would it be feasible to give it another go at resolving this bug? |
Beta Was this translation helpful? Give feedback.
-
In my opinion there are three major areas of basic functionality that need to be addressed: The first is having manually unwire all event handlers specified in the XAML. Not being able to use x:Bind and having to manually unhandle all events that are specified in the XAML code on a window closed so that the objects are properly garbage collected is a major undertaking and major step back from previous frameworks. The second issue is not having a proper transparent background for owner drawn windows with a proper pass thru when clicking on the transparent portion of the window. While it is possible to work around (Big thanks to @castorix for your swapchainpanel implementation. It was a big help in this area.) it's crazy to have to go through such an elaborate workaround to accomplish what was basic functionality for over a decade in WPF. The third major area is the complete lack of any helpers on the Window and AppWindow classes for some of the basic functionality that's existed for years. Having to constantly pinvoke into User32 to handle what feels like basic window functionality is a major difficultly. Need a min/max height/width well you need to hook into the message loop and handle the MINMAXINFO. Need to not have a window show up in the taskbar better call GetWindowLong and SetWindowLong to turn on the TOOLWINDOW style. etc. Under WPF these were simple properties on the Window, but after years of development on the Windows App SDK we still need to have manually handled all of these "basics" pieces of functionality in Win32 method calls. If you want developers to move off of WPF to WinUI and the Windows App SDK right now you should really focus on the making the existing functionality work and improving some of the basic functionality that those developers are familiar with. Otherwise, they simply continue with WPF and not migrate to the new platform. |
Beta Was this translation helpful? Give feedback.
-
Do you mean Segmented control in the WindowsCommunity package? Or is it a new control in Winui itself? |
Beta Was this translation helpful? Give feedback.
-
This community call was a complete waste of time!Question people prepared here in this thread or directly in the call have been completely ignored. |
Beta Was this translation helpful? Give feedback.
-
The call was ended because "there are no more questions". Guys, you didn't look into this thread nor did you properly scan the live chat for questions. It's really disappointing that you call this a community call and then flat out ignore the community. |
Beta Was this translation helpful? Give feedback.
-
Where was @ryandemopoulos , I miss him. |
Beta Was this translation helpful? Give feedback.
-
I assume this thread will be closed down soon so I created #8927 Community calls and questions. |
Beta Was this translation helpful? Give feedback.
-
How insanely out of touch are you guys with the general feeling from your involved developers (i.e. us)? What is the point of announcing the Community Call and soliciting feedback for it to be entirely ignored? I'm amazed that you guys ignore the top rated posts ITT. Clearly there is a large amount of dissatisfaction with the progress and management of WinUI - please affect positive change and address the numerous issues around management, communication, backlog, etc. What is the point of having issues enabled here if you're not going to use them? The backlog on Github is just going to get back to the state that it was. Can we at least get bi-directional updates in place so that when the team is looking at an issue in ADO we can see progress on GH? And I'm still waiting to hear how many people are actively working on this product.... |
Beta Was this translation helpful? Give feedback.
-
Better than previous calls. Definitely, they have taken some positive steps, heard the community, restructured things. They have a direction now. |
Beta Was this translation helpful? Give feedback.
-
Actually I liked the session, if I have to point out something negative, it would be that widening the call into Windows Developer Community, with not all projects being WinUI related, kind of points out not having that much content for WinUI to fill in a hourly call, and since the team is responsible for all of those projects, raises again the question of how many of those FTEs are actually doing WinUI specific work. |
Beta Was this translation helpful? Give feedback.
-
Please join us for the September 2023 edition of the WinUI Community Call. This event will be live-streamed to YouTube: https://www.youtube.com/watch?v=_m-EnEfG88g
Details
Date: Sept 27, 2023
Time: 16:00-17:00 UTC (9:00-10:00am Pacific)
Anyone and everyone is welcome - no pre-registration is required.
This will be an informal interactive live stream directly with members of our engineering team.
Format
The community call is a call among the WinUI team that is live-streamed onto YouTube. We present on new updates, share information, welcome guests, and answer your questions.
Agenda
Q&A Code of Conduct
Leave us your questions in the comments on this issue or live in the YouTube chat during the stream!
Beta Was this translation helpful? Give feedback.
All reactions