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 164900 - gtkfilechooserbutton doesn't allow save-action
gtkfilechooserbutton doesn't allow save-action
Status: RESOLVED NOTABUG
Product: gtk+
Classification: Platform
Component: Widget: GtkFileChooser
3.22.x
Other All
: Normal normal
: ---
Assigned To: gtk-bugs
: 662837 (view as bug list)
Depends on:
Blocks: 164617
 
 
Reported: 2005-01-22 13:41 UTC by Ronald Bultje
Modified: 2017-08-27 09:44 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Ronald Bultje 2005-01-22 13:41:26 UTC
Hi,

It seems that in G2.10, GnomeFileEntry is deprecated in favour of
GtkFileChooserButton, which is a good thing. However, I can only select folders
and open files with it, I can't create new folders or save to new files (see
http://cvs.gnome.org/viewcvs/gtk%2B/gtk/gtkfilechooserbutton.c?rev=1.26&view=markup,
gnome_file_chooser_button_new(), the g_return_val_if_fail()). Since the entry is
deprecated, this seems like a regression to me. Is there some other object I
should use or is this unfinished code?
Comment 1 Matthias Clasen 2005-01-22 14:11:59 UTC
The code to do this was in the GtkFileChooserButton for a while during 2.5.x, but
the interaction designers found that it promotes bad ui, and thus it was removed
before 2.6.
Comment 2 Ronald Bultje 2005-01-22 15:05:30 UTC
Hi Matthias,

thanks for the response. I assume discussing this here is not really a good
thing, so where would I ask questions on how to do this instead? gtk-devel-list?
The usability people? Somewhere else? I need such a widget (I think), or
something that resembles it.

Thanks.
Comment 3 Matthias Clasen 2005-01-23 03:18:26 UTC
I think it might make sense to discuss options for save mode in the migration
guide. I think Seth and jrb had some ideas how one would handle save mode.
Comment 4 Daniel Boles 2017-08-27 09:42:01 UTC
*** Bug 662837 has been marked as a duplicate of this bug. ***
Comment 5 Daniel Boles 2017-08-27 09:44:42 UTC
In response to that later request for this to be added, I'll leave this closed unless anyone wants to reconsider it, but this was my take on it before finding this (again), and it seems to agree that it wasn't considered a useful design.


I guess the FCB was intended for a file-opening workflow, where maybe you select the file, then select some options (e.g. which things to load), then click OK.

As far as I've seen, saving tends to work in the opposite order: You select the options for what you'e saving, then click OK, then get a FileChooser.

So it might be that these actions were considered but not deemed useful.

Perhaps you could give an example of a useful workflow/design that would use the FileChooserButton in save (or even create folder) mode, and explain why it's preferable to the other, currently available ways of doing this.