Linux

4889 readers

2 users here now

Shit, just linux.

Use this community for anything related to linux for now, if it gets too huge maybe there will be some sort of meme/gaming/shitpost spinoff. Currently though… go nuts

founded 2 years ago

MODERATORS

carrot@sh.itjust.works

How do I disable the file type filter in KDE's file picker? (sh.itjust.works)

submitted 4 days ago* (last edited 4 days ago) by DeltaWingDragon@sh.itjust.works to c/linux@sh.itjust.works

3 comments fedilink hide all child comments

When I open a "Save" dialog, or a file selection dialog, only one type of file is shown. Sometimes it even filters by the extensions.

I don't want this! This isn't Windows, where file extensions really matter! How do I disable the filtering, or set it to show "All Files" by default?

The "Save Page" dialog: you'd think there are only 2 files here, both .html files

Nope! There's lots of stuff!

you are viewing a single comment's thread
view the rest of the comments

[–] grue@lemmy.world 1 points 1 day ago

What I want is to set the default filter to “All Files” for every application that uses the file picker. I don’t want to do it per application. If there’s a setting for the file picker itself, I want to use that.

It’s not just the save dialog, I mentioned the file selection dialog (for uploading) in the post. The Librewolf “save page as” is just one singular example, not the entire problem!

Oh! In that case, KFileDialog might actually be (roughly) the part you want to patch.

(That was just what I found in a couple of minutes of looking, BTW. I've never programmed anything related to KDE -- not even applications, let alone the library itself -- so do your own research. I'm just going by generic software engineering principles, not anything specific to how KDE works, either technically or administratively.)

What would the effects be?

Depends on exactly which bits you change. The "save" dialog probably inherits from an abstract dialog or something. If you change the base class everything will be affected; if you change the derived class only the derived class will be affected. The trick is to find the right layer in the hierarchy that changes everything you want while leaving everything else alone.

How would I go about this? Would I need to alter the source code and recompile? What would happen when I update the software?

Yes, you'd have to alter the source and recompile. At that point, you're basically maintaining your own small private fork of the software, so you'd have to merge your changes back in on each update.

Alternatively, you could try to get the KDE project to accept the changes, but I have no idea how receptive they would be.

“Saving HTML files with their file extension” can still be accomplished if I can see all the files at once. I’m not changing the extension, I just want to see where I’m putting them. There is no reason why viewing all files would prevent me from saving the same file types together.

If you're saying that you'd like to decouple the filter of what file types you can see from the filter of what file types you can save as, that's interesting. It might have merit in terms of user experience, but I suspect it might be a slightly more invasive change to code -- and an even more invasive change to the public-facing API, which developers of applications that use KDE might have something to say about.