https://bugs.kde.org/show_bug.cgi?id=492007
--- Comment #4 from kde.bugs@mattbaker.digital --- In addition to the single threading, from my perspective, it seems wrong that pressing F2 does not immediately display the rename dialogue before doing anything else. Should the source metadata-read only occur if the pattern options require it? If they are basic options already stored in the local DB, could it not skip the full metadata-read? If the patterns are changed by the user from something that requires additional metadata to something that is already in the local DB, then the existing additional metadata-read operation should be aborted. If additional metadata information is required, it would be nice if the rename list/table in the rename dialog highlighted the current files that it is reading for additional data with a small status string displaying what is occurring. I know this is no small task to implement and just intended as a suggestion. -- You are receiving this mail because: You are watching all bug changes.