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 587288 - dialogue are created with "Has Separator" False and throw warning on the console
dialogue are created with "Has Separator" False and throw warning on the console
Product: glade
Classification: Applications
Component: general
git master
Other Linux
: Normal trivial
: ---
Assigned To: Glade 3 Maintainers
Glade 3 Maintainers
Depends on:
Reported: 2009-06-29 10:18 UTC by Michele Mattioni
Modified: 2010-03-27 18:56 UTC
See Also:
GNOME target: ---
GNOME version: ---

Description Michele Mattioni 2009-06-29 10:18:38 UTC
I found out that everytime a new dialogue is created in glade the "Has Separator" button is written in bold and the value is No.

It seems like the User has made a change but that is not the case.

The downside of this is that the dialogue throw a warning as soon the glade file has been parsed like the one below:

GtkWarning: Ignoring the separator setting

I proposed to set the value of the button to Yes so the warning is not anymore print on the console.
Comment 1 Pietro Battiston 2009-11-12 23:12:43 UTC
Michele, could you give an example of how to reproduce?

I mean: by interpreting your report, I would assume that by

1) starting Glade
2) clicking on a new dialog
3) saving
4) loading the created glade file

one would see 

./test:10: GtkWarning: Ignoring the separator setting

in the console.

Instead, that doesn't seem to happen, at least with glade 3.6.3... and notice that some glade files on my system _do_ give this warning.
Comment 2 Pietro Battiston 2009-11-13 08:01:04 UTC
OK, I got the point: the warning is raised only when some GtkMessageDialog has those "separator settings".

So there is no need to change anything for ordinary GtkDialogs... though I also see no particular reason to set the button to Yes (which is different from the default).
Comment 3 Garrett Regier 2009-11-29 22:04:56 UTC
A GtkMessageDialog sets priv->ignore_separator so glade should not show the set separator.

The reason that setting it to Yes results in so errors it because glade only saves what it needed and thus avoids setting the separator and causing the waring.

  if (priv->ignore_separator)
      g_warning ("Ignoring the separator setting");

  _gtk_dialog_set_ignore_separator (GTK_DIALOG (dialog), TRUE);
Comment 4 Tristan Van Berkom 2010-03-27 18:56:12 UTC
Fixed in master (disabled the property).