WPF Community-run projects

[gurpreet-wpf]

[!!!UPDATE!!!]

We've realized that the term "community run projects" is a broad term and is open to different interpretations by developers. However, the intended meaning of this term was to have a channel through which we can prioritize issues/PRs that the community thinks would improve WPF over other existing open PRs/issues (https://github.com/orgs/dotnet/projects/146).

In future, we'll refer to such initiatives by a different name (TBD - To Be Decided) which may be less ambiguous.

Full description here: #7130 (reply in thread)

Original Post

Hello,

We are thrilled to announce that WPF is planning to start community-run projects which would be chosen and run by the community. This is in continuation to our efforts of increasing engagement with our community and to maximize and recognize your contributions which would help the overall community.

We are planning to start first project for our upcoming release i.e. NET 7.0. Issues/Bugs (excluding feature requests/enhancements) will be chosen based on the upvotes/likes/reactions by the community and will be up for grabs for all our active contributors. We will try to close the PRs submitted for these issues on priority basis.

Start submitting the issues you want to be addressed by commenting them here below this post.

Scope of work items for this project:
1. Issues
2. Bugs

Not in scope:
1. Feature requests
2. Enhancements

Thanks!

[wstaelens]

XPS issues:

1. XPS documents memory leak (System.Windows.ContextLayoutManager+LayoutQueue+Request and XpsDocument.GetFixedDocumentSequence()) #6301
2. XPS documents in .NET Core can't be opened #3546

(3. #4000 )
🤞

[lindexi]

• The first point in StylusPlugin is wrong when use the high DPI #6415

[lindexi]

• WPF will have a touch offset after trun on the WM_Pointer message #3360

[lindexi]

• WPF can not receive the touch message when set WS_EX_TRANSPARENT to window #3145

[lindexi]

• Known issue: WPF Image memory leak when remove image from visual tree #2397

[lindexi]

• The main thread of the WPF application that starts automatically at boot will forever wait for the touch thread to execute #3147

[lindexi]

• Image Source fails to load an image if application path has hash sign in it #6560

[olowk]

XPS documents memory leak (System.Windows.ContextLayoutManager+LayoutQueue+Request and XpsDocument.GetFixedDocumentSequence())

[olowk]

XPS documents in .NET Core can't be opened

[JosefNemec]

Laggy user experience when using VRR display

[cbaysinger]

Bugs:
Touches from dialog window get "stuck" in main window #450
Click event is rarely raised when using touch #194

[michael-hawker]

There's already been discussion in the .NET repo here: dotnet/runtime#18087 with a community member engaged to work on it with a draft PR (dotnet/runtime#65101).

They also want to fix it for WPF, but I believe need some support. Would be great to get some support and commitment from the WPF team to make this 6 year old request happen for .NET 7 (since it was originally pulled from .NET 5 dotnet/corefx#35772).

WPF Issue: #1887
WPF PR: #6097

[Symbai]

First post says out of scope are feature requests and enhancement (which I personally find extremely disappointing). What you mention is unfortunately not a bug or issue so it would be out of scope. Like almost everything else people waiting for for a long time now.

[michael-hawker]

I would still argue it's a long-standing bug that the interface isn't respected. It's definitely a feature in .NET itself, but it's a bug in WPF that the interface isn't respected which would enable that feature.

Plus, there's already a community member up for helping on this one, so I think it fits the brief well.

[darcome]

Enhancement:
Create a control that can be used to embed 3d engines. Most of them create their own main window and cannot be embedded in wpf windows or other controls.

The control should be a surface that 3d engines would use to present their data.

The control should also be compatible with WinUI3 and MAUI.

[batzen]

Fixing TextBoxView memory leak for 2 seconds after unloading host control #1161

[batzen]

Select all text on triple click when no rich content #1163
=> I don't consider this a new feature but an accessibility bug fix

[bgrainger]

• Eliminate allocation in StreamAsIStream.Read #6632

[bgrainger]

• Eliminate memory copy when reading font data #6254

[bgrainger]

• Use params and char overload #4231

[bgrainger]

• Fix create BitmapDecoder with async file stream. #4966

[bgrainger]

• Using the Clone method to fast clone the array in StylusPoint #5218

[bgrainger]

• Optimize the code of OSVersionHelper #6252

[bgrainger]

• Use span slice instead of substring in AbbreviatedGeometryParser.ReadNumber #6272

[bgrainger]

• Some improvements to FrugalList #6280

[bgrainger]

• Change most non-generic sorts to be generic #6285

[bgrainger]

• Avoid Hashtable-related allocations in AccessorTable #6500

[bgrainger]

• Avoid Hashtable-related allocations in DataBindEngine #6501

[bgrainger]

• Stop boxing WeakReferenceListEnumerator in PresentationSource use #6502

[bgrainger]

• Avoid delegate allocation to call ListCollectionView.PrepareComparer #6511

[gurpreet-wpf]

Thanks everyone for submitting their responses. We are triaging the issues and PRs mentioned here. In order to kickstart the next steps, we would be closing this discussion now. However, if you still want to submit any more issues, feel free to comment here by 22nd June 2022. Thanks!

[wstaelens]

really hope for the XPS issues/improvements. 10k+ customers would for sure benefit from this. 🤞

[gurpreet-wpf]

Hi All,

We have triaged all the responses we have received here and based on the feasibility, we have selected a total of 24 PRs which would be tracked as part of this project -> https://github.com/orgs/dotnet/projects/146

We are targeting to close majority of these PRs within next 3 CTPs. [Sep 22]

Thanks