Hi Matthijs ten Kate I am glad to see a response on this issue.
My intention is that "Simple Scan" implies to simply scan a document. Nobody expects that "Simple Scan" is an document based application like libre office, audacity or sublime text. Instead you expect that it scans a document, shows it to you and than you can press save and it will be saved to disk. For this I replaced the 'save' functionality by the 'save as' functionality, because a document saved as file could be replaced by a new scanned image and 'saved' as the same file, which the user does not expect as explained. Save as is a better choice. This opens a dialog, asking you for a file name with a pretty good preset and in most cases you simply press enter to acknowledge it to save a new file. In my mind it actually fix both bugs. Robert 2017-03-29 13:24 GMT+02:00 Matthijs ten Kate <[email protected]>: > Thanks Robert for looking into this. > However, I'm not sure how removing the 'Save As' functionality fixes the > issue. Can you elaborate on this? > Furthermore, bug 1672019 is just a small part of the issue described here. > > Interestingly, the "save-behaviour" of Simple Scan seems to vary between > output formats: > > PDF - behaves as in this bug report > PNG & JPG - behaves as reported in bug 1672019 > > I never noticed this before since I rarely save to PNG or JPG. > > It would be great to have both bugs fixed after having been present for > over 6 years... > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/842076 > > Title: > Save button doesn't warn before overwriting existing file > > Status in Simple Scan: > Fix Committed > > Bug description: > Usability bug: In a typical serial scanning workflow, one tends to scan > a document, click on the 'Save' icon, navigate to the location where the > document should be stored, enter the name of the document and finally click > on the 'Save' button. So far so good. > After that, one typically moves on to the next document, which typically > needs to be saved to a different file. > Currently however, when scanning a second document, it is displayed next > to the first. Other than that, there is no indication whatsoever that > Simple Scan will overwrite the previously saved document as soon as the > user clicks the 'Save' icon. > > So the user will typically remove the first page(s) which he/se > presumes are safely stored in a file and hit 'Save' again... > > Moreover, if the user isn't paying close attention, he/she could run > into the situation that numerous scans have been made and presumably > saved, only for the user to find out that only the *last* scan was > actually saved and all previous scans were overwritten. > > I've run into this 'bug' numerous times and so have other people in my > environment who have been using the application in this manner. > IMHO there are numerous ways to 'fix' this: > 1. Always warn before overwriting an existing document. In an > application as simple as Simple Scan, I cannot imagine why anyone would > want to have the 'Save' icon/button working the way it does now when > scanning multiple documents. > 2. Clearly show which saved document the user is currently working on > (e.g. display the file name in the menu bar). > 3. Find a way to make absolutely clear to the user (at the first use of > the application?), that the workflow for serialized scanning of documents > is using a 'CTRL+N' (for new document) after EACH scan. > > A combination of the above would of course also be a solution. > > ProblemType: Bug > DistroRelease: Ubuntu 11.10 > Package: simple-scan 3.1.5-0ubuntu1 > ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4 > Uname: Linux 3.0.0-10-generic x86_64 > Architecture: amd64 > Date: Mon Sep 5 20:33:53 2011 > DriverPackageVersions: > libsane 1.0.22-2ubuntu1 > libsane-extras N/A > hplip 3.11.7-0ubuntu5 > hpoj N/A > InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 > (20110803.1) > MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-10-generic > root=UUID=24ee2295-58ad-4d06-a4eb-c0c7359e2bb6 ro quiet splash > vt.handoff=7 > SourcePackage: simple-scan > UpgradeStatus: Upgraded to oneiric on 2011-09-01 (3 days ago) > dmi.bios.date: 01/17/2011 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: P1.30 > dmi.board.name: H67M-GE > dmi.board.vendor: ASRock > dmi.chassis.asset.tag: To Be Filled By O.E.M. > dmi.chassis.type: 3 > dmi.chassis.vendor: To Be Filled By O.E.M. > dmi.chassis.version: To Be Filled By O.E.M. > dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.30:bd01/17/2011: > svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.: > rvnASRock:rnH67M-GE:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: > dmi.product.name: To Be Filled By O.E.M. > dmi.product.version: To Be Filled By O.E.M. > dmi.sys.vendor: To Be Filled By O.E.M. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/simple-scan/+bug/842076/+subscriptions > -- GPG-Key: 00E68CA6 -- You received this bug notification because you are a member of Simple Scan Development Team, which is a bug assignee. https://bugs.launchpad.net/bugs/842076 Title: Save button doesn't warn before overwriting existing file Status in Simple Scan: Fix Committed Bug description: Usability bug: In a typical serial scanning workflow, one tends to scan a document, click on the 'Save' icon, navigate to the location where the document should be stored, enter the name of the document and finally click on the 'Save' button. So far so good. After that, one typically moves on to the next document, which typically needs to be saved to a different file. Currently however, when scanning a second document, it is displayed next to the first. Other than that, there is no indication whatsoever that Simple Scan will overwrite the previously saved document as soon as the user clicks the 'Save' icon. So the user will typically remove the first page(s) which he/se presumes are safely stored in a file and hit 'Save' again... Moreover, if the user isn't paying close attention, he/she could run into the situation that numerous scans have been made and presumably saved, only for the user to find out that only the *last* scan was actually saved and all previous scans were overwritten. I've run into this 'bug' numerous times and so have other people in my environment who have been using the application in this manner. IMHO there are numerous ways to 'fix' this: 1. Always warn before overwriting an existing document. In an application as simple as Simple Scan, I cannot imagine why anyone would want to have the 'Save' icon/button working the way it does now when scanning multiple documents. 2. Clearly show which saved document the user is currently working on (e.g. display the file name in the menu bar). 3. Find a way to make absolutely clear to the user (at the first use of the application?), that the workflow for serialized scanning of documents is using a 'CTRL+N' (for new document) after EACH scan. A combination of the above would of course also be a solution. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: simple-scan 3.1.5-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4 Uname: Linux 3.0.0-10-generic x86_64 Architecture: amd64 Date: Mon Sep 5 20:33:53 2011 DriverPackageVersions: libsane 1.0.22-2ubuntu1 libsane-extras N/A hplip 3.11.7-0ubuntu5 hpoj N/A InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110803.1) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-10-generic root=UUID=24ee2295-58ad-4d06-a4eb-c0c7359e2bb6 ro quiet splash vt.handoff=7 SourcePackage: simple-scan UpgradeStatus: Upgraded to oneiric on 2011-09-01 (3 days ago) dmi.bios.date: 01/17/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.30 dmi.board.name: H67M-GE dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.30:bd01/17/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH67M-GE:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/simple-scan/+bug/842076/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~simple-scan-team Post to : [email protected] Unsubscribe : https://launchpad.net/~simple-scan-team More help : https://help.launchpad.net/ListHelp
