Bug 240252

Summary:	Disable resorting after rename
Product:	[Applications] gwenview	Reporter:	RalphB <pub>
Component:	general	Assignee:	Gwenview Bugs <gwenview-bugs-null>
Status:	REPORTED ---
Severity:	wishlist	CC:	ashark, bugmenot, hamboy95, myriam, pub, virtuousfox
Priority:	NOR
Version First Reported In:	2.4
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description RalphB 2010-05-31 18:34:36 UTC

Version:           2.4 (using KDE 4.4.2) 
OS:                Linux

After renaming an image, the files in the current directory are resorted while the cursor remains on the file just renamed. While this sounds plausible at first, it is actually detrimental when working with multiple files.

As an example, I often want to give more descriptive names to the images I download from my digital camera. I thus start with a folder of files all named DSC*.JPG. I would enter view mode, and then repeatedly hit F2 to enter a new name, hit Next to advance to next image, hit F2 to enter a new name, hit Next to advance to the next image, and so on. This won't work, however, if files are resorted on-the-fly, as Next will not advance to the next unprocessed image. In fact, you absolutely lose track of where you are, both in view mode and in browse mode. Simply not resorting images, however, would work wonderfully in this scenario.

Suggestion: Do NOT resort images after rename automatically, or at least do not resort when in view mode; only resort when pressing Refresh. The best solution would be to add an option "[ ] resort automatically".

Alternatively, if resorting is considered essential functionality, adapt the focus handling so that the focus is set on the image *after* the file just renamed.

Reproducible: Always




OS: Linux (i686) release 2.6.32-22-generic
Compiler: cc

Comment 1 Sergey Kondakov 2010-10-27 18:22:31 UTC

yes, this is pretty stupid and i have no idea why someone thought it's right thing to do. looks like one more consequence of that someone's experiment "101 way to break file mamagment/make konqueror suck in new version of KDE".

if it not clear why this sucks - one more example: recently i tried renaming bunch of files with names starting on "s" to names starting on "A" in a directory with _thousands_ of files. it was so painfull that i actually remembered "explorer" :\

Comment 2 Jekyll Wu 2011-12-15 00:05:46 UTC

*** Bug 289008 has been marked as a duplicate of this bug. ***

Comment 3 Mark S. 2011-12-28 00:39:30 UTC

Because this doesn't document a "broken" feature or a glitch in gwenview, this should be moved to the wishlist

Comment 4 RalphB 2011-12-28 15:08:17 UTC

Well, I don't quite agree with your recent reclassification of "wishlist".

The renaming functionality of Gwenview is just broken when dealing with multiple files. And to quote from the bug tracker's help page:

Severity: Normal
regular issue, some loss of functionality under specific circumstances

Please kindly reconsider your classification of this issue.

Comment 5 Justin Zobel 2021-03-09 02:32:41 UTC

Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.

Comment 6 Andrew Shark 2023-08-23 00:24:48 UTC

It still resort the just renamed image. But it is probably a normal behavior. If you want to keep it at place, I think it is better to change the sorting mode. For example, sort by date, and start renaming your files.

Gwenview: 23.07.80