Symbai

Instead of these two boolean properties I would prefer `BorderThickness` (set to 0 to hide the borders) and `UnderlineColor` + `UnderlineFocusedColor` (set to transparent to hide it). This supports much...

If this gets added I hope its more than just an integer spinner. A good NumericUpDown is difficult. It must support all kind of value types (float, integer, double etc)....

> If the WPF team would be interested in a PR i would be happy to create one. You know the WPF team batzen... If you write this here you...

As you can see in batzen's PR #5610, the WPF team is ignoring him. Not only the PR is not getting reviewed, they even don't answer his questions. Also see...

> To be clear, `BinaryFormatter` APIs will never be removed. Setting a switch in .NET 9 to enable the `BinaryFormatter` will likely become required for WPF and WinForms Looks like...

> @Symbai the API surface will still be there, you'll just need the package for the APIs to work. Which is exactly what I said for option B.

> Any progress ？ Obviously not. WPF might be open source but repo got owned by WinUI team and they don't know much about C# or WPF. For new features...

Jesus, this looks so "over complicated ". Instead of a single line we have now 8 lines to write... for EVERY single textblock. Also in your example it trims at...

> So I guess you can do `` That is pretty cool, thank you. I hope the docs will show this example. While its cool that you can do crazy...

And when the instruction has no prefix? I can change the proposed property to nullable byte so that it only returns the offset if its possible and null when its...