| Summary: | Add confirm overwrite option for kdialog --getsavefilename | ||
|---|---|---|---|
| Product: | [Applications] kdialog | Reporter: | benedictleejh |
| Component: | general | Assignee: | Brad Hards <bradh> |
| Status: | REPORTED --- | ||
| Severity: | wishlist | CC: | cfeck, justin.zobel |
| Priority: | NOR | ||
| Version First Reported In: | 1.0 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
benedictleejh
2014-08-02 10:04:19 UTC
Hm, wouldn't it make sense to always ask for this confirmation? In other words, instead of adding a --confirmoverwrite option, we could change the defaults, and add a --noconfirmoverwrite option. Opinions? I second that. To me, a default asking for confirmation and --noconfirmoverwrite option would make more sense. I was originally proposing based on a backward compatibility point of view. Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone! Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone! Testing on Plasma 5.14.3 suggests that kdialog now has a confirm overwrite option for the save file dialog. Looking at the help though, I can't find a --noconfirmoverwrite option, for those who might want it. I'm not too concerned, because it's probably better to make sure the user really wants to overwrite an existing file, but there might be those who do want it. I'll leave it to the maintainers to decide if this issue can be considered closed (since it's technically fixed) and those who want a --noconfirmoverwrite should open another issue or not. |