RAccessibility requirements
NI guess I have to push my engine without audio for now 
Nseems daunting to add audio support and I don't want to duck tape some old library
RIt's probably more worth it to them for them to use the inbuilt ones for accessibility reasons which would be significantly easier and more consistent and reliable for them
RI hate apps that don't use platform-native dialogs
RGIMP is really annoying for me on Windows since it uses the GTK file picker instead of the Win32 one
RI hate ones that use the windows dialog
REspecially that folder browser one
Nthe really old one?
Nthats just a square window?
RYes
Noh man I feel you
RThat you just can't paste a path into
RThe Windows one is really elegant for me since I can always type in the file name I want to open and it auto-completes
Rinstead of needing to read through the list of existing files (which the gtk one makes you do in some cases)
NI feel like that thing existed way back in the DOS era of windows
NI also don't like non-native looking dialogs
RMe neither
RI like apps being consistent with the OS's theme
RBut anything is better than that dialogue
Ntrue
Nthats why I had Windows App SDK support on my engine
RAnd I don't like writing my own dialog systems (especially file pickers), that's a lot of needless work when your OS has an API for that.
RI actually hate the modern windows win32 theming
Nas for Linux, I had my friend make bindings for
nativefiledialogs-extendedGitHub
Full .NET wrapper for NativeFileDialogs (Extended). - GitHub - Speykious/NativeFileDialogs.NET: Full .NET wrapper for NativeFileDialogs (Extended).
ROh I do too
RThey removed context menu item highlights in Windows 11
ROr if it's still there
Rit's so faint
Rit may as well NOT be there
RThey keep brighting up the color scheme
RTo the point where it just toasts your eyes
RAt this point I'd rather design an app with my own design, language and style. Then I would try and use Windows built-in stuff
RThat's not even the issue for me because I can just invert it
Na lot of Windows 11 UI feels like they're using XAML Islands to wrap over the old stuff
RThe issue is I can barely see the white mouse cursor against the white context menu and there's no item highlight
NI managed to open a Windows Explorer window without the ribbon
Rso I can't be reasonably sure I'm hovering over the thing I wanna click
RIf you futz with certain system files and the registry, it's possible to devolve the Windows 11 taskbar back to being a (broken) Windows 10 one
RYou may actually be right
Nprobably the reason why they're pushing Windows App SDK so much
Nit used to be called Project Reunion
Lwell thats what MAUI is supposed to be for but it doesnt support linux
Nto unify Win32, UWP, WPF together
LMAUI is generally what they want to push for UI stuff
RThing is I would prefer not to use a full UI framework if at all possible
Rbecause that just adds a lot of bloat if all I'm using it for is system dialog abstractions
Lbest bet is to then call into something like GTK or QT that is cross platform
N@acidiclight btw
NI forgot which GUI libraries this interfaces for Linux but it works okay for Windows and MacOS