After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 366342 - Sound juicer shuold have an "overwrite all" option when replacing files
Sound juicer shuold have an "overwrite all" option when replacing files
Status: RESOLVED DUPLICATE of bug 130782
Product: sound-juicer
Classification: Applications
Component: interface
2.16.x
Other All
: Normal minor
: ---
Assigned To: Sound Juicer Maintainers
Sound Juicer Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-10-28 15:20 UTC by Raptor Ramjet
Modified: 2007-10-13 21:15 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description Raptor Ramjet 2006-10-28 15:20:42 UTC
When ripping a CD Sound Juicer will prompt you if a destination file exists asking whether you want to overwrite the existing file.  The only available buttons on the prompt are "yes" and "no" and the same prompt is issued for each and every file.

When the prompt is given to the user there should also be options for "Overwrite all", "Overwrite non" and "Quit".  Once again it is extremely tedious to be prompted for each and every file.  As the user I know whether I want to overwrite the existing files or not and I really, really don't need to be asked for every single file.

Of course I realise that I could delete the existing files before starting the ripping process but the interface should give me the option to replace them without being prompted for each file.

Personally I believe that any program that sequentially processes a list of objects using a GUI should adhere to the following design logic.

1  Process next item in the list.
2  If a prompt for user intervention is required allow options to specify that the action applies either to all items, no items, yes for a single item, no for a single item or quit processing (i.e. "All", "None", "Yes", "No", "Quit")
3  If an error occurs whilst processing an item either fail the entire operation or store the error (logging it as it occurs) but only report the errors to the user once once the list has been processed. (i.e. Do not use an error prompt for each individual item)

I'm afraid that GNOMEs philosophy of "process only one item at a time" (which is prevalent through out the whole interface) is one of the major usability issues I have with it.  It's an outdated design philosophy.




Other information:
Comment 1 Michael Chudobiak 2007-10-13 21:15:45 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 130782 ***