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

            Bug ID: 510808
           Summary: In Export to Local Storage, if a Target Location does
                    not exist, a confusing error message is shown
    Classification: Applications
           Product: digikam
      Version First 8.9.0
       Reported In:
          Platform: Microsoft Windows
                OS: Microsoft Windows
            Status: REPORTED
          Severity: minor
          Priority: NOR
         Component: Usability-Ergonomy
          Assignee: [email protected]
          Reporter: [email protected]
  Target Milestone: ---

Created attachment 185910
  --> https://bugs.kde.org/attachment.cgi?id=185910&action=edit
Example expected result

SUMMARY
When I try to use Export to Local Storage feature, I am able to manually type
in a target location. If there are errors in that entry (such as a nonexistent
destination), a very confusing error message is shown which does not lead me to
realize the root cause. 

STEPS TO REPRODUCE
1.  Open Export to Local Storage
2.  Manually Type in a path for Target location, such as "C:\NewFolder"
3.  Click "Start Export"

OBSERVED RESULT
Error Window: “Some of the items have not been copied and are still in the
list. You can retry to copy these items now.”

--> Discussion: This message asks the user to try again. But in this case,
repeated clicking "Start Export" will simply result in this error window
reappearing again, thus throws the user into confusion. 

EXPECTED RESULT
(a) A prompt asking if the user wishes to create the non-existent directory, OR
(b) A specific error message saying "Export failed - C:\NewFolder does not
exist.", OR
(c) A message is shown to the user BEFORE they have clicked Start Export button
(see attached mockup image)


SOFTWARE/OS VERSIONS
Windows: 11, 24H2

ADDITIONAL INFORMATION

The code in
https://invent.kde.org/graphics/digikam/-/blob/master/core/dplugins/generic/webservices/filecopy/fcexportwindow.cpp#L235
seems to suggest that the window currently have no visibility as to the reason
for incomplete exports, thus a generic error message is shown. 

Perhaps a function could be added in `slotTargetUrlChanged()` to check if the
target exists? This way, a notice message could be shown unobtrusively to the
user, as in the mockup?

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

Reply via email to