WPF Migration

[cyanfish]

Possibly targeted for version 8.0. Benefits include better UI performance in general, hardware acceleration, better image processing performance/quality, and avoiding GDI+ issues (e.g. global locks, lack of thread safety). As Eto supports WPF the migration work only needs to cover custom platform-specific code.

Tasks:

• NAPS2.Images.Wpf
• Custom UI components
  • Toolbars
  • Listviews
  • Notifications
  • Misc
• Worker
  • Ideally use the Win32 API directly instead of WinForms/Wpf, so an eventual migration from .NET Framework will not require an extra 50MB for a 32-bit copy of WinForms/Wpf.
• Evaluate hardware acceleration
  • Ideally we can find a workaround for the issue of Nvidia thinking anything hardware accelerated is a game and needs fps counters etc.

[cyanfish]

After re-evaluating WPF and upcoming improvements to Windows Forms (e.g. built-in dark mode support) I've decided the best long-term strategy is to stay on WinForms.