[Bug / Feature Request]: The `KryptonOpenFileDialog` can have poor performance on some OS hardware

[Smurf-IV]

I have noticed that the KFOD has lot's of flickering issues on some installations of Windows 10.
So much so, that it has to be disabled.

Proposal:

1. Recreate the Open / save / Folder Dialogs with "Normal" krypton controls

• e.g. https://www.telerik.com/support/code-library/fileexplorer-demo-application
• 

2. Use WindowsAPICodePack and wrap the controls from that "https://github.com/dbarros/WindowsAPICodePack/blob/master/Samples/ExplorerBrowser/CS/WinForms/ExplorerBrowserTestForm.Designer.cs
3. Investigate the used of a themed WebBrowser

• https://www.vbforums.com/showthread.php?597434-RESOLVED-Windows-File-Explorer-Control

4. Rework a WPF project:

• https://www.codeproject.com/Articles/770837/WPF-x-FileExplorer-x-MVVM-2
• 

5. Something else ?

[Smurf-IV]

@Wagnerp thoughts ?

[PWagner1]

@Smurf-IV I think the first option would offer greater flexibility or number 2 or 4. I do currently have a somewhat 'modern' implementation (converted to .NET) of WindowsAPICodePack here. What are your thoughts?

[Smurf-IV]

My vote is something along the lines of

• Use 4 as a guide
• ReWork to be 1

The use of the ###CodePack requires DirectX and thirdparty, and some fixing for the build for AnyCPU usages (It's possible just go and look how lzma is done)

Which ever is chosen, it will be Big, and will take a while, so I'll probably start it in Easter '24.

[PWagner1]

@Smurf-IV There could also be an 'Extended Toolkit' version, which could include a ribbon for common commands.

[Smurf-IV]

That's getting closer to a Full Browser replacement.
Which means it would have to have a working List view that does the following as well:

And this sort of thing for Win 11 emulation:

[giduac]

Hi @Smurf-IV,

Is this a necessity for V90 or can this wait until V100?
Please tag the ticket accordingly, ty.

[Smurf-IV]

Due to the upheaval, I think the rewrite should be V100, but any performance improvements for v90....