[question] why not fork Ava's controls completely.?? leave the bug fix burden of controls to them..??

[blackholeearth]

i honestly love winforms easy of use. its nice initiative.

but it fells like the bugs will never end. they keep cropping up. so simple behaviors cause behavioural bugs.

• i have discovered new bug...
  • combobox popupWindow's scrollbar is not released if ms up is done outside of ScrollBar Area #92
    • 5 years has passed at Avalonia, i assume their combobox (also other controls) doesnt have these issues.

it looks like this(bug madness) will never end??

---

question??::

why not fork Ava's controls completely.??
leave the bug fix burden of controls to them..??

lets take whats good from there ,, remove the xaml nuisanse.???

edit:

• actually Ava has fluent coding style for controls...

https://github.com/AvaloniaUI/Avalonia.Markup.Declarative

can we take this code. build winforms layer on top of it ???
hide all these WPF xaml hassle .

make it usable like winforms,

[jpobst]

Trying to force a very different toolkit into a "winforms-looking API" is likely a very difficult project, and isn't the goal of Modern.Forms. If someone wants to start a different project that attempts to do that, more power to them.

Avalonia is a great toolkit and if it meets your needs then you should absolutely use it. It's a mature project with a decent amount of resources behind it.

Modern.Forms on the other hand literally has as the first line of its readme:

*** This framework is currently in its early stages. Use at your own risk. ***

It is not mature, not widely used, and has no resources behind it. It will have tons of bugs and missing functionality. At its current stage it is likely not suitable for anything more than small hobby projects.