On Tue, 2009-05-05 at 19:16 +1200, Rob Brown-Bayliss wrote:
> On Mon, 2009-05-04 at 20:06 +1200, Rob Brown-Bayliss wrote:
>
> I have tracked it down to a bug in glade. I am using Glade 3.6.1 on
> Ubuntu 9.04
There is a build of Glade 3.6.3 which appears to fix the problem.
--
Rob Brown-Bayli
On Mon, 2009-05-04 at 20:06 +1200, Rob Brown-Bayliss wrote:
I have tracked it down to a bug in glade. I am using Glade 3.6.1 on
Ubuntu 9.04
What has been happening is each time I change the UI via glade, it has
been removing the signal for the delete-event and destroy-event from the
xml file it
Rob Brown-Bayliss wrote:
> print "="
> print "Count = " + str(self.check_count)
> self.check_count += 1
> print self.wtree.get_widget("label_checkbutton")
> print "="
> if self.wtree.get_widget("label_checkbutton").get_active(
Rob Brown-Bayliss schreef:
>
> Hi,
>
> I have this code being called every few minutes by a gkt timeout function:
You can try to put this in your __init__()
self.label_checkbutton = self.wtree.get_widget("label_checkbutton")
Then you don't need to get the widget everytime and it cannot fail.
>
>
Hi,
I have this code being called every few minutes by a gkt timeout
function:
print "="
print "Count = " + str(self.check_count)
self.check_count += 1
print self.
