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 676488 - InfoBar's content-area and action-area packing tags are unhandled.
InfoBar's content-area and action-area packing tags are unhandled.
Status: RESOLVED FIXED
Product: glade
Classification: Applications
Component: general
git master
Other Linux
: Normal normal
: ---
Assigned To: Glade 3 Maintainers
Glade 3 Maintainers
Depends on:
Blocks:
 
 
Reported: 2012-05-21 12:28 UTC by Jo-Erlend Schinstad
Modified: 2013-05-19 10:03 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Jo-Erlend Schinstad 2012-05-21 12:28:14 UTC 
This may or may not be a bug in Glade, but I'm unable to find out. The problem is with InfoBar. Glade adds

<child>
    <object class="GtkInfoBar" id="infobar1">
        <child internal-child="content_area">
            <packing>
            </packing>
        </child>

        <child internal-child="action_area">
            <packing>
            </packing>
        </child>

When you try to load the UI definition using Gtk.Builder.add_from_file, then it complains about those two packing tags. The precise error message is: Unhandled tag 'packing'. 

Commenting them out removes the issues. But of course, that means a lot of manual editing of XML-files all the time, so it's a very annoying bug.

I don't know if content-area and action-area should have a packing tag. If they should, then it's a bug in GTK+. If they shouldn't, it's a bug in Glade.
Comment 1 Tristan Van Berkom 2013-01-23 04:47:43 UTC 
You cannot configure the way GtkInfoBar packs it's internal children into itself.

If there are <packing> elements (as specially empty ones ??) then that is a bug in Glade.

Thanks for reporting these.
Comment 2 Tristan Van Berkom 2013-05-19 10:03:42 UTC 
I can't reproduce this... here is the output of a naked GtkInfoBar output
from Glade:

<?xml version="1.0" encoding="UTF-8"?>
<interface>
  <!-- interface-requires gtk+ 3.10 -->
  <object class="GtkInfoBar" id="infobar1">
    <property name="visible">True</property>
    <property name="app_paintable">True</property>
    <property name="can_focus">False</property>
    <child internal-child="content_area">
      <object class="GtkBox" id="infobar-content_area1">
        <property name="can_focus">False</property>
        <property name="spacing">16</property>
        <child>
          <placeholder/>
        </child>
        <child>
          <placeholder/>
        </child>
        <child>
          <placeholder/>
        </child>
      </object>
      <packing>
        <property name="expand">True</property>
        <property name="fill">True</property>
        <property name="position">0</property>
      </packing>
    </child>
    <child internal-child="action_area">
      <object class="GtkButtonBox" id="infobar-action_area1">
        <property name="can_focus">False</property>
        <property name="orientation">vertical</property>
        <property name="spacing">6</property>
        <property name="layout_style">end</property>
        <child>
          <placeholder/>
        </child>
        <child>
          <placeholder/>
        </child>
        <child>
          <placeholder/>
        </child>
      </object>
      <packing>
        <property name="expand">False</property>
        <property name="fill">True</property>
        <property name="position">1</property>
      </packing>
    </child>
  </object>
</interface>

I'm not sure how this happened for you, but it seems the bug has
fixed itself over time.

Please feel free to reopen if this happens again.