Anyone noticed a winui4 issue tag is secretly added?

[HO-COOH]

What does this mean? WinUI3 is going to be finally deprecated by Microsoft again? (Why am I not even surprised?)

[kitUIN]

UWP: waiting for you

[ghost1372]

Oh, WinUI 4! I had a feeling they were working on something, especially since after version 1.6, there was no roadmap, no answers to questions, and no community calls. And now version 1.8 is all about AI, so I can guess something is going on—maybe they'll announce it alongside the new Visual Studio preview?
I don't care whether it's WinUI 3, 4, 5, or any other version—just fix the basic issues and add new features already. The title bar has supposedly been getting fixed since version 1.6, and it's still not done.

[ghost1372]

Breaking changes... interesting.

[Gaoyifei1011]

Oh, WinUI 4! I had a feeling they were working on something, especially since after version 1.6, there was no roadmap, no answers to questions, and no community calls. And now version 1.8 is all about AI, so I can guess something is going on—maybe they'll announce it alongside the new Visual Studio preview? I don't care whether it's WinUI 3, 4, 5, or any other version—just fix the basic issues and add new features already. The title bar has supposedly been getting fixed since version 1.6, and it's still not done.

It turns out that there has been no trace of the UI controls TableView, PagerControl and InkCanvas to this day. At least some of the implementation code for InkCanvas and PagerControl still exists, while TableView has no messages at all.

------------------------

原来关于 UI 控件的 TableView、PagerControl 和 InkCanvas 也至今没有任何下落。InkCanvas、PagerControl 至少还有部分实现的代码，TableView 没有任何消息。

[ghost1372]

@Gaoyifei1011 I think they're currently focused on AI-related work, and we might see some new developments after version 1.8.
I've been using the PagerControl for months.

https://github.com/ghost1372/DevWinUI/tree/main/dev/DevWinUI.Controls/Controls/Ported/PagerControl

[jamespack]

It's been there for like 4 or 5 years. Go look at the issues labeled with it.

[ghost1372]

It's been there for like 4 or 5 years. Go look at the issues labeled with it.

Maybe the label was renamed. Also, a new issue was created two days ago that has this label, so even if it was an old one, it's active now!

[Gaoyifei1011]

I hope that WinUI 4 can fully integrate WinUI 2(UWP/Xaml islands) and WinUI 3 through substitution or redirection (Windows.UI.Xaml.dll redirects to Microsoft.UI.Xaml, etc.) At least it won't make these two UI frameworks seem so disconnected

------------------

我希望 WinUI 4 能完全融合 WinUI 2(UWP / Xaml islands) 和 WinUI 3，通过替代或者重定向的方式（Windows.UI.Xaml.dll 重定向到 Microsoft.UI.Xaml 等等），至少不会让这两套 UI 框架显得如此割裂

[wherewhere]

We need LTS .NET, Built-in WinRT, Full .NET Compatible AOT, System GUI Platform, System Managed Window and a trusted Microsoft Store...

[marcelwgn]

The tag wasn’t added secretly - it has existed for several years to mark issues or changes that are breaking in nature and therefore deferred to a future major release (originally labeled as "WinUI 4") in line with semantic versioning.

To avoid confusion around roadmap or version plans, we’ve since renamed the tag to "breaking change", with the label description:
“This is a breaking change that should be considered for a major revision in future.”