https://bugs.kde.org/show_bug.cgi?id=523704
--- Comment #3 from Roland <[email protected]> --- If I could offer a suggestion- Its unusual to have mixed functionality (context sensitive rename). And where that may make sense here, where you have object (folder/tag) rename as alt-enter since bulk isnt really an options that needs expansion. file renaming does. And while I understand that the convention for a file rename is F2, and it would be more consistent to have batch rename as something else- F5 or whatever, F2 can work. People would argue that OK, well, you can select the last-used pattern for single files in a folder just as you can for a single-selected file in a group of files vs F2. And OK- great. But Id simply suggest this isnt as simple as it seems. If I load a group of folders for example, or restructure an existing branch. there are going to be non-consistent structures where a name pattern isnt going to work. Example: Sports Football Collegiate School Name Player NFL Patriots Players Tennis Collegiate Pro Players (***) So I end up with this structure because there are no pro teams in tennis, and changing the naming convention for players in sports isnt obvious now. Worse, if I have a less structured setup for more generic content- it can easily be the case that I have an inconsistent structure with leaves that have single entries- not because I failed to better-combine categories, but because I have a structure that isnt fully populated with images (restructure, where some dragging is needed, or tag-based searches, or imported data etc). Now, stepping through that tree, there are any number of folders that may be renamed, or re-ordered, and where there may be 1 image in a folder for reasons defined. I cannot simply show all as Include Album Subtree, because the bulk rename pattern wont work for varied structures. And in almost all cases, probably 95% or more, the file name is going to be based on the folder structure. Metadate about the file is going into Descripton (file level) so that this doesnt change with folder restructure, and so that this is pinned to the photo on export. Having the bulk rename function revert to manual file rename every time is silly. It doesnt make sense to infer this as a desired function when in most cases, you are going to want something basic for certain types of single-file folders- perhaps just [dir] #. But with that intermixed with other folders that have better established paths where they might be [dir...] [dir] #, you cannot just select all from an Album Subtree select. You could, but you dont know if the file name makes any sense. Often Ill set these up as [dir] # (To be Tagged), and then deal with tagging or sorting later via filters) So, I would suggest that you do one of a few things: 1. Add a standard Filename option to the rename list, and pin that to top of list, and persist last used pattern for F2 globally 2. Add a radio button for Pattern Rename vs Single File Rename and persist that for F2 globally) 3. Change from this mixed function Bulk vs Single rename. Use F2 for single object rename (folders, files, tags), and Alt Enter for Bulk etc. I dont see downside in option 1. There are problems with the existing approach of both not persisting the selection, but also in that if you have a large folder, and you select a single file in that group (say 1000 files), and you scroll around in that folder, hitting F2 brings up the file rename dialog. Except, it is for the active file, and the scroll position doesnt reindex. So you dont really know what you are renaming. Maybe 123089naerli.jpg -> Sports, Tennis, name.jpg. There is no indication in the rename for where this came from. And you may think- OK, well, its inferred from the selected folder. No, it isnt, because in SubFolder mode, you have a listing of a slew of folders. Yes, there are segmentations within the thumbnail display, but the problem still exists- you dont know which file, in which 'section' is selected, so you have to use a workaround (i.e. select another parent folder and move back to reindex etc. Maybe that is a bug that deserves it own entry, but its one of many challenges with this assumption that F2 makes sense as an object AND a bulk rename without either a persist option or a radio butto. Roland -- You are receiving this mail because: You are watching all bug changes.
