Re: [gtk-list] Qt succeeds where gtk fails... (callbacks)
- From: "Cody A. Russell" <bratsche dfw net>
- To: gtk-list redhat com
- Subject: Re: [gtk-list] Qt succeeds where gtk fails... (callbacks)
- Date: Fri, 2 Jul 1999 11:39:25 -0400 (EDT)
There are numerous programs available that make use of continuous timeouts
in GTK+ that do not suffer from this problem. I made my PPP applet use
timeouts to control animation and never had this problem. It's more likely
that the programs you listed have a bug in them that is killing the
timeout at some point.
Cody
On Fri, 2 Jul 1999, Eric Livingston wrote:
> GTK seems to develop amnesia on me and "forget" that programs such as
> gpppkill and gstripchart have one-second timeout callback functions that
> they use to update their displays. They both start fine, but after several
> seconds, they stop updating. Inserting some printfs here and there has led
> me to realize that after a short time, gtk simply stops calling the
> functions, even if the timeout functions consistenly return non-zero
> values (thus, they should not be unregistered).
>
> I just downloaded and am testing a Qt program called pppload, which does
> similar things to gpppkill, and which I can also set to update every
> second.
>
> That program has been working fine now for over an hour.
>
> I'm beginning to think very strongly that there is a fundamental flaw in
> how gtk is handling its callbacks...
>
> Can anyone guide me in trying to debug this further? I've already
> determined that the select() function seems to be working fine on my box,
> so it's got to be somewhere else in gtk where this problem manifests...
>
> Eric Livingston
>
>
> --
> To unsubscribe: mail -s unsubscribe gtk-list-request@redhat.com < /dev/null
>
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]