Summary: | Gwenview: use same sort order as current Dolphin view | ||
---|---|---|---|
Product: | [Applications] gwenview | Reporter: | Dotan Cohen <kde-2011.08> |
Component: | general | Assignee: | Gwenview Bugs <gwenview-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | wishlist | CC: | ashark, christoph, david.cortes.rivera, drikqlis, frederick888, KaiUweBroulik2, kde-2011.08, kde, kdudka, kirill.knize, lists, magnedj, mustart, nate, notmart, pavel.datsenko, r2b2x3+kdebug, rebel, ricardo, smowtenshi, tagwerk19, tynach2 |
Priority: | HI | Keywords: | usability |
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Unlisted Binaries | ||
OS: | Unspecified | ||
Latest Commit: | https://invent.kde.org/graphics/gwenview/-/commit/ec1de82c418512b4ae4782b429310acd4822ac6d | Version Fixed In: | 21.08 |
Sentry Crash Report: | |||
Attachments: | attachment-14767-0.html |
Description
Dotan Cohen
2010-05-02 19:49:45 UTC
I agree. I don't understand why there isn't more people complaining about this. *** Bug 250079 has been marked as a duplicate of this bug. *** *** Bug 249573 has been marked as a duplicate of this bug. *** Fixed in https://bugs.kde.org/show_bug.cgi?id=343452 *** This bug has been marked as a duplicate of bug 343452 *** This is not what the other bug is about, reopening. My mistake, sorry. *** Bug 371950 has been marked as a duplicate of this bug. *** *** Bug 361029 has been marked as a duplicate of this bug. *** *** Bug 365683 has been marked as a duplicate of this bug. *** *** Bug 390201 has been marked as a duplicate of this bug. *** Created attachment 112018 [details] attachment-14767-0.html I have checked in KDE 17.10, but the same problem still exists. Can I help You with screenshots or list of alphabetical sort order example of gwenview? 9719Pecs_d1399 good morning.JPG 9b10Pecs_d3790 bemutatom Hajnit.JPG 9814Vp_d1985 a profi.JPG 9813Vp_d1976 jo.JPG a502Pecs_d7781.JPG a715A_a2603_2M.jpg I prefer use alpabetical sort order by char after char as ascii codes. Musulin, Béla --- 2018-03-05 13:07 GMT+01:00 Dr. Chapatin <bugzilla_noreply@kde.org>: > https://bugs.kde.org/show_bug.cgi?id=236059 > > Dr. Chapatin <bugseforuns@gmx.com> changed: > > What |Removed |Added > ------------------------------------------------------------ > ---------------- > CC| > |david.cortes.rivera@gmail.c > | |om > > --- Comment #10 from Dr. Chapatin <bugseforuns@gmx.com> --- > *** Bug 390201 has been marked as a duplicate of this bug. *** > > -- > You are receiving this mail because: > You are on the CC list for the bug. > I'm affected by this bug as well. I have a lot of image files that are named by their md5 hashes in hexadecimal, and this effectively means that I get names in a seemingly random order in Gwenview only. It's EXTREMELY annoying. Also affected by this, I often search for images spread over a few subfolders and it would be really great if I could use the back and forward buttons in Gwenview for navigating my search results rather than having to close Gwenview before opening it again by double-clicking another image in the Dolphin search results. * one way may be gwenview just reading and writing the sort order from dolphin settings (either .directory of the folder or global .local/share/dolphin/view_properties/global/.directory depending on dolphin settings) which sounds kinda error prone... * another way may be dolphin launching gwenview with parameters about sorting, though would need a lot of special casing in KRun * another way could be dolphin exposing a dbus service to ask about "what are the view properties for this folder?" which would require some back and forth between dolphin and gwenview, but may perhaps be a bit safer. another thing is: what should happen when the sort order is changed in gwenview? i guess it should not change what dolphin does i guess (In reply to Marco Martin from comment #14) > * one way may be gwenview just reading and writing the sort order from > dolphin settings (either .directory of the folder or global > .local/share/dolphin/view_properties/global/.directory depending on dolphin > settings) which sounds kinda error prone... > > * another way may be dolphin launching gwenview with parameters about > sorting, though would need a lot of special casing in KRun > > * another way could be dolphin exposing a dbus service to ask about "what > are the view properties for this folder?" which would require some back and > forth between dolphin and gwenview, but may perhaps be a bit safer. > > > another thing is: what should happen when the sort order is changed in > gwenview? i guess it should not change what dolphin does i guess I'd absolutely expect the Dolphin sorting order not to change if changing the sorting order within Gwenview. (In reply to Marco Martin from comment #14) > * one way may be gwenview just reading and writing the sort order from > dolphin settings (either .directory of the folder or global > .local/share/dolphin/view_properties/global/.directory depending on dolphin > settings) which sounds kinda error prone... > Consider that Gwenview might be opened by a method other than from Dolphin. > * another way may be dolphin launching gwenview with parameters about > sorting, though would need a lot of special casing in KRun > Despite the complexity, this makes sense. > another thing is: what should happen when the sort order is changed in > gwenview? i guess it should not change what dolphin does i guess I agree that this should not affect Dolphin. A possibly relevant merge request was started @ https://invent.kde.org/graphics/gwenview/-/merge_requests/80 Git commit dbabe22249781242c789d691c1f887046e71580e by Nate Graham, on behalf of Marco Martin. Committed on 04/06/2021 at 12:04. Pushed by ngraham into branch 'master'. Add SortOrderForUrl method to DBus interface adds a method to ask what's the sorting strategy (column and order) for a particular Url, as Dolphin can have directory-specific sorting strategies This makes possible for other apps that have lists of files, like Gwenview to use the same sorting when invoked from dolphin, ie opening an image M +12 -0 src/dbusinterface.cpp M +2 -0 src/dbusinterface.h M +7 -0 src/global.cpp M +2 -0 src/global.h https://invent.kde.org/system/dolphin/commit/dbabe22249781242c789d691c1f887046e71580e Implemented by Marco Martin with the combination of https://invent.kde.org/system/dolphin/commit/dbabe22249781242c789d691c1f887046e71580e in Dolphin and https://invent.kde.org/graphics/gwenview/-/commit/ec1de82c418512b4ae4782b429310acd4822ac6d in Gwenview, for version 21.08 for both of them! (In reply to Nate Graham from comment #19) > Add SortOrderForUrl method to DBus interface Will this stretch as far as fixing Bug 417730? After updating to 21.08 it works for almost every sorting expect for sorting by Modified date from oldest to newest (from newest to oldest it works ok). After upgrading to 21.08 I observed that sorting by file type also doesn't apply to Gwenview. It uses the default one by file name ascending. I must be using Gwenview in a very different way than the people complaining here: I use it a lot for lectures, having folders with alphabetically named symbolic links. I've been using Gwenview for years for this, but now I suddenly need to manually sort each subfolder because Gwenview **overrides its own settings** with what happens to be the current Dolphin settings. This is extremely counterintuitive for somebody who hardly uses Dolphin (I mostly use the cli). Can you please find a solution which: - doesn't have Gwenview ignore its own settings (which is a huge no-no in any book) - makes this behaviour an option if it is really needed for Dolphin-Gwenview integration, but then reflects this in Gwenviews settings menu ? thanks ! Joost. (currently running version 21.08.1 in Arch Linux) Can you please file a new bug report for that? Thanks! ok, apologies, I'm new to this ;) No worries! new bugreport: https://bugs.kde.org/show_bug.cgi?id=443168 (In reply to JoostR from comment #29) > new bugreport: > https://bugs.kde.org/show_bug.cgi?id=443168 I really think we should just revert that, read the other bug and the duplicates, I fail so see why it should be synced that way, given we do that nowhere else. This is not completely fixes. Follow the Bug 466836. |