(11-17-2022, 09:01 PM)Spriggsy Wrote: Now, I will say it only looks out of place to me because the save button still brings up the old dialog rather than a save file dialog box.
The problem with that one is that it's harder, or maybe not possible, to force a file type, like what kind of text file. The "MIME" database on some Linux distros is really skewed up. Especially after Wine is installed it becomes happy setting file associations that it really shouldn't such as "INI" to fire up the Wine Notepad or "HTML" to try to open the Internet Explorer emulation that doesn't work most of the time. If I'm not mistaken the function call for save-file dialog out of "tinyfiledialogs" illustrates this problem. It supports one "suggestion" for a file type which the user of the compiled program doesn't have to follow because "All Files" is always available.
On WindowsXP the programmer was allowed to give a long text entry delimited with pipes or ASCII0 for each file suffix he/she wished filtered into the displayed file list, to increase the chance a file was saved with the expected suffix. Now at least on Linux with one of the text editors ("xed" at this moment on EndeavourOS), it's either "Text files" or "All files". And through the "MIME" the system really doesn't care what is a text file, with suffix "TXT", "BAS", "C", "LUA", if it's "readme.md" or much more.
What is irritating about all of this on Linux is that some file managers attempt to guess what kind of text file, eg. they detect "#" as the very first character of the file. If "include" follows then they surmise it's a C/C++ source code file. This is possible with Freebasic source code too. If "!/bin/bash" follows or maybe just the exclamation point then that file is decorated as "bash" script even if that "executable" text file could fire up "gawk" or Lua instead. An EXE file could be mistaken for a self-extractable archive even with Wine installed but that's another point entirely.
