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 542298 - "Print to File" output file selection is difficult to use
"Print to File" output file selection is difficult to use
Status: RESOLVED FIXED
Product: gtk+
Classification: Platform
Component: Printing
3.2.x
Other All
: Normal minor
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2008-07-10 02:57 UTC by Matt McCutchen
Modified: 2012-09-04 11:29 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Attachments
gtk print dialog (48.57 KB, image/png)
2012-01-27 16:37 UTC, Marek Kašík
Details
save dialog (42.23 KB, image/png)
2012-01-27 16:37 UTC, Marek Kašík
Details

Description Matt McCutchen 2008-07-10 02:57:15 UTC
I find the controls for specifying the output file of a "Print to File" difficult to use.  Once I go to "Save in folder -> Other...", it is easy to forget that I am supposed to specify the containing folder rather than the output file itself.  As a result, I accidentally created a folder with the name I wanted for the output file and had to go and delete the folder before proceeding.  No other application I have seen has such a strange manner of specifying an output file.

Here are some possible ways to improve the interface:

1. Remove the "Other..." menu option and add a "Browse..." button that opens a standard Save dialog and fills both the "Name" and "Save in folder" fields based on the result.

2. Remove all of the file selection controls and launch a Save dialog when the user clicks the "Print" button.  This has the advantage that, if a warning about replacing an existing file appears, the file-chooser dialog is still open to provide context.

3. Integrate a full file chooser into the Print dialog.  To do this without making the General tab overly large, I suggest adding a row at the top that says "Print to: ( ) Printer ( ) File" (radio buttons) and showing either the printer list or the file chooser in the area underneath as appropriate.

Other information:
Comment 1 Máirín Duffy 2012-01-25 16:09:38 UTC
this bug is still an issue. and it sucks. and it effects my work almost daily. i wasted 10 minutes today manually cleaning up the folders this dialog created when i thought i was choosing a file name.

i think this bug is filed against the wrong component; i am moving it from gnome-print to GTK / apologies in advance if its the wrong component.
Comment 2 Matthias Clasen 2012-01-25 18:48:53 UTC
Marek, can you look at this ?
Comment 3 Marek Kašík 2012-01-27 16:37:02 UTC
Created attachment 206282 [details]
gtk print dialog

What about something like on the picture?
Comment 4 Marek Kašík 2012-01-27 16:37:32 UTC
Created attachment 206283 [details]
save dialog

And this one.
Comment 5 Máirín Duffy 2012-01-27 16:48:37 UTC
Hi Marek! I really appreciate your quick attention to this bug!!!

Can you help walk me through the screenshots you posted?

My concern with attachment 206282 [details] is that I'm not sure where the filename 'gtk-demo.pdf' came from - is that what would be input in attachment 206283 [details]?

Attachment 206283 [details] looks good to me, if it would replace the current dialog. So if I click "Save As...", then I can select the folder the document will go in and type out the filename I want it to have, press 'Save', and it will just work, right?

That sounds perfect to me and matches the File Save dialogs other GTK apps use.
Comment 6 Sebastian 2012-08-20 07:42:36 UTC
Hi there is a working patch + screenshot for this problem in bug #682129. I did not know about this bug, so I reopened a new one, we should mark this bug as a duplicated.

Anyway, the discussion is to remove these options entirely and modify the "Print" button in such a way that is displays save and offers a "save file" dialog when clicked. This would be much easier to use.

The details can be read at bug #668529, I have already prepared a first patch.
Comment 7 Sebastian 2012-09-02 13:09:03 UTC
I would save this is fixed by 4c67e71c63aca1770a6a486c30653f831a0191bd and can be closed.
Comment 8 Marek Kašík 2012-09-04 11:29:00 UTC
> I would save this is fixed by 4c67e71c63aca1770a6a486c30653f831a0191bd and can
> be closed.

Hi, you are right. I'm closing this one.

Marek