https://bugs.kde.org/show_bug.cgi?id=491778
Frederic Da Vitoria <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Status|RESOLVED |REOPENED Resolution|DUPLICATE |--- --- Comment #3 from Frederic Da Vitoria <[email protected]> --- I understand your comment about the workflow and I agree that what I did was wrong. But: The current situation is misleading because DK behaves exactly as if it had applied the modifications, when it hasn't really done so. I feel that writing to the .xmp file doesn't count because most users don't check their folders frequently with a file manager, so that the user is left with the impression that everything went as intended and the .xmp file will never be seen (AFAIK DK doesn't use an isolated .xmp file, and it is probably best this way). IMO, it is a software's responsibility to prevent the user from doing things which can't be correct, or at least warn the user when something has gone wrong. So in this situation, I can see 4 different ways to improve things, if there are pending modifications, either: a. Disable moving images entirely. This solution works, but the user may not understand why moving is disabled. Don't forget that users aren't always quite dedicated to what they are doing so imagine doing a few edits, answering a phone call, and then returning to DK and go on with moving the images; the user could very well at that point forget about the pending edits and be puzzled by DK's silent refusal to move files. b. Upon moving, DK could display a message saying the move operation is impossible because there are pending modifications, and not perform the move operation. This is the solution which I would find best because the user knows what is wrong but hasn't lost his modifications (yet). c. When the move operation has been performed, display a message saying the modifications have been canceled because of the move. This solution is not as good as options a or b, because redoing the canceled edits can be tricky, but at least the user is warned. d. Apply the modifications automatically, which would not be a good idea IMO. It would break the workflow, and it would make the confirmation kind of useless. -- You are receiving this mail because: You are watching all bug changes.
