Public bug reported:

Binary package hint: glade-3

See here for valid list store types:
http://www.pygtk.org/docs/pygtk/class-gtkliststore.html#method-gtkliststore--set-column-types

As you can see, gobject.PyObject is an acceptable value.
If I hand-edit the glade XML file it works:
  <object class="GtkListStore" id="files_liststore">
    <columns>
      <!-- column-name Name -->
      <column type="gchararray"/>
      <!-- column-name Size -->
      <column type="gchararray"/>
      <!-- column-name Object -->
      <column type="PyObject"/>
    </columns>
  </object>

But if I save the file in glade, it erases the type:
  <object class="GtkListStore" id="files_liststore">
    <columns>
      <!-- column-name Name -->
      <column type="gchararray"/>
      <!-- column-name Size -->
      <column type="gchararray"/>
      <!-- column-name Object -->
      <column/>
    </columns>
  </object>

Note: this is with the GtkBuilder settings, not libglade.

GTK fully supports objects store in the liststore and so does the glade
XML, only the UI seems to be missing the type.

This works fine as well when not using a model built by the glade interface:
gtk.ListStore(str, str, object)

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: glade 3.7.0.is.3.6.7-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.35-25.44-generic-pae 2.6.35.10
Uname: Linux 2.6.35-25-generic-pae i686
Architecture: i386
Date: Wed Jan 26 16:56:16 2011
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: glade-3

** Affects: glade-3 (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: apport-bug i386 maverick

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glade-3 in ubuntu.
https://bugs.launchpad.net/bugs/708398

Title:
  Glade list model editor lacks PyObject support

-- 
desktop-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

Reply via email to