https://bugs.kde.org/show_bug.cgi?id=524367

            Bug ID: 524367
           Summary: On moving a file out of the digikam environment via
                    its GUI, certain ops (like bulk rename) fail and dont
                    infer a cause
    Classification: Applications
           Product: digikam
      Version First 9.2.0
       Reported In:
          Platform: Microsoft Windows
                OS: Microsoft Windows
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: AdvancedRename-engine
          Assignee: [email protected]
          Reporter: [email protected]
  Target Milestone: ---

DESCRIPTION
On right click drag from digikam out to say the desktop (maybe a
transfer/staging area for different instances). Digikam doesnt register this
internally (requires an F5/refresh). Maybe its not possible to implement a
check real time on a drag->move if that is lower level OS file system. But if I
have say 10 files in a folder, and drag one out, and then select all for batch
rename, the engine will error that 1 file is in error. This becomes a problem
if you are doing restructuring over some time, and you dont refresh the whole
system (which can take some time with a lot of files). A later bulk rename
fails, which is difficult when you are doing a branch build rename via Incldue
Sub-Album Tree.

It may make sense to have an error message expansion, or to actually parse
errors to determine if an F5/rescan is needed etc. At least then the user can
understand this isnt a naming conflict with file or folder.



STEPS TO REPRODUCE
1.  Pick any folder with multiple files, and drag->move one file out of the
system (i.e. to desktop folder)
2. Select all files in the album, hit F2, and use some rename pattern for batch
rename


OBSERVED RESULT
Error is created that 1 file cannot be renamed

EXPECTED RESULT
No error. System should either ignore a file rename error if the return is
'file not found', or the system should run a background scan on the source
folder if a right click and drag is detected with no drop event- which might be
an aborted move, but may be a move out of the system. Worst case, the
warning/error dialog should define root cause (1 file not found, please refresh
folder)

SOFTWARE/OS VERSIONS
Operating System (available in the Info Center app, or by running `kinfo` in a
terminal window):
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to