lottanzb team mailing list archive

[Severin Heiniger <severinheiniger@xxxxxxxxx>]

The bug has been marked as a duplicate upstream. The problem is that the
"name" property is only meant to be used w.r.t. themes and doesn't need
to be unique. The GtkBuilder ID however needs to be unique and was bound
to the "name" property until now.

This means that the problem can be fixed within LottaNZB using a rather
ugly hack by getting the GtkBuilder ID using
gtk.Buildable.get_name(widget). Let's hope that the GTK/PyGTK API's will
be updated regarding this issue by adding methods/functions like
"get_id" or "get_buildable_id".

** Changed in: lottanzb
       Status: Invalid => Triaged

** Changed in: lottanzb
       Status: Triaged => In Progress

** Changed in: lottanzb
     Assignee: (unassigned) => Severin Heiniger (lantash)

** Changed in: lottanzb
   Importance: Undecided => Critical

** Changed in: lottanzb
    Milestone: None => 0.5.3

-- 
Widget names not set when using GtkBuilder
https://bugs.launchpad.net/bugs/507739
You received this bug notification because you are a member of LottaNZB
Development Team, which is subscribed to LottaNZB.

Status in GTK+ GUI Toolkit: Unknown
Status in LottaNZB • Automated Usenet Client: In Progress
Status in “gtk+2.0” package in Ubuntu: Invalid
Status in “lottanzb” package in Ubuntu: Invalid
Status in “pygtk” package in Ubuntu: Invalid

Bug description:
LottaNZB cannot be launched on an up-to-date Lucid machine because of a bug in GtkBuilder. I tracked down the problem:

When loading a XML UI file using GtkBuilder, the 'name' property of widgets isn't set. On the other hand, the 'name' property of 'GtkAction' objects is properly set.

A test case written in both Python and C is attached. Compare the output on a Karmic and a Lucid machine.

I'm pretty sure that LottaNZB worked about a week ago, when I initially installed Lucid. This means that the bug could have been introduced in a recent update.