Bug 409771 - Set of available columns in details views should be editable
Summary: Set of available columns in details views should be editable
Status: CONFIRMED
Alias: None
Product: frameworks-kio
Classification: Frameworks and Libraries
Component: Open/save dialogs (other bugs)
Version First Reported In: 5.245.0
Platform: Arch Linux Linux
: NOR wishlist
Target Milestone: ---
Assignee: KIO Bugs
URL:
Keywords:
: 494328 (view as bug list)
Depends on:
Blocks:
 
Reported: 2019-07-13 14:23 UTC by Patrick Silva
Modified: 2025-05-17 09:45 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
screenshot (196.44 KB, image/png)
2019-07-13 14:23 UTC, Patrick Silva
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Patrick Silva 2019-07-13 14:23:02 UTC
Created attachment 121499 [details]
screenshot

STEPS TO REPRODUCE
1. open kate
2. press ctrl+0 to open file open dialog
3. set details view mode
4 . click "Sorting" button in the tool bar

OBSERVED RESULT
As we can see in the attached screenshot, "Sorting by type" is available but there is no "Type" collumn in the files view.

EXPECTED RESULT
Files view has "Type" collumn

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.16.3
KDE Frameworks Version: 5.60.0
Qt Version: 5.13.0
Comment 1 Nate Graham 2019-07-15 21:13:40 UTC
From the code, this looks intentional. It's a trivial fix, but I think I might see why it was removed. The set of columns is non-editable, so if we added it, it would always be there, which could be kind of annoying since it's a low-value column.

We should make the set of columns editable, then people can add them column for themselves if they want it.
Comment 2 Patrick Silva 2021-09-18 19:48:47 UTC
it's still not editable. :(

Operating System: Arch Linux
KDE Plasma Version: 5.22.90
KDE Frameworks Version: 5.86.0
Qt Version: 5.15.2
Graphics Platform: Wayland
Comment 3 Patrick Silva 2025-05-17 09:45:10 UTC
*** Bug 494328 has been marked as a duplicate of this bug. ***