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 610925 - GtkFileChooserDialog won't pick show-hidden setting from a GtkBuilder file
GtkFileChooserDialog won't pick show-hidden setting from a GtkBuilder file
Status: RESOLVED FIXED
Product: gtk+
Classification: Platform
Component: Class: GtkBuilder
unspecified
Other Linux
: Normal normal
: ---
Assigned To: GtkBuilder maintainers
GtkBuilder maintainers
Depends on:
Blocks:
 
 
Reported: 2010-02-24 11:11 UTC by Alberto Ruiz
Modified: 2015-07-24 02:00 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
show-hidden files test case (746 bytes, text/plain)
2015-06-24 20:16 UTC, Alberto Ruiz
Details

Description Alberto Ruiz 2010-02-24 11:11:41 UTC
When you create a filechooserdialog or a filechooserbutton the show hidden property is ignored (defaults to not, and shows them anyway).

The property does however update if you change it.
Comment 1 Alberto Ruiz 2015-06-23 14:15:10 UTC
This is still the case for Glade 3.18
Comment 2 Alberto Ruiz 2015-06-24 20:16:01 UTC
Created attachment 306047 [details]
show-hidden files test case

I need to better explain the problem perhaps, I realize it's not so clear from the way I wrote it 5 years ago.

Basically it doesn't matter which setting you choose in the builder file for show hidden files, at run-time Gtk+ won't pick it up.

I'm attaching a gjs test case for reference.
Comment 3 Alberto Ruiz 2015-06-24 20:29:47 UTC
According to tristan on IRC this bug belongs to Gtk+
Comment 4 Matthias Clasen 2015-07-23 11:54:35 UTC
The reason for this is that show-hidden is persisted in a setting, and the settings get loaded on map. show-hidden appears to be the only setting that is also programmatically settable and thus the only to have this problem. We could add an 'explicitly set' flag and ignore the setting in that case.
Comment 5 Alberto Ruiz 2015-07-23 12:14:29 UTC
(In reply to Matthias Clasen from comment #4)
> The reason for this is that show-hidden is persisted in a setting, and the
> settings get loaded on map. show-hidden appears to be the only setting that
> is also programmatically settable and thus the only to have this problem. We
> could add an 'explicitly set' flag and ignore the setting in that case.

FWIW I don't have strong opinions here, I just found it really odd that Glade would offer the switch and then was completely ignored.