← Back to team overview

simple-scan-team team mailing list archive

[Bug 842076] Re: Save button doesn't warn before overwriting existing file

 

As of version 3.2.1-0ubuntu2 found in precise, this is still quite
annoying usability wise.

Meaning you open Simple Scan, do your scans, save them, delete some or
all of them (selection wise) because you want to scan some other things,
then you press "Save" and you up to repeating all the scans you did
before, at least when the number of new scans is equal or higher then
the old ones.

To get it right you are forced to open a new scan, then it won't just
overwrite, but after delete scans in Simple Scan there is no visual
indication that would distinguish those modes. So it just too easy to
miss and this is really an usability nightmare, as users probably can
get quite angry about that behavior, as you will loose too easily
already done work.

The easiest fix would probably to always prompt when overwriting. Maybe
that would also be the best in terms of interaction with other programs,
just think about scanning, editing some files with GIMP without changing
filenames and continue with other scans.

-- 
You received this bug notification because you are a member of Simple
Scan Development Team, which is the registrant for Simple Scan.
https://bugs.launchpad.net/bugs/842076

Title:
  Save button doesn't warn before overwriting existing file

Status in Simple Scan:
  In Progress

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