If you are inside the gtk main loop, timeouts should be getting serviced
correctly. If you are not in the gtk main loop, then timeouts will not
get serviced on time (they will be called next time you get into the main
loop with a call to mainloop() or mainiteration()).
I don't know about the SIGALRM signal (note that unix signals are totally
different from GTK+ signals). It may work or it may not. I don't think
gtk uses alarm(), so you could probably use it to perform actions at
certain intervals during long calculations.
James.
--
Email: [EMAIL PROTECTED]
WWW: http://www.daa.com.au/~james/
On Mon, 25 Oct 1999, Jozsa Kristof wrote:
> On Mon, Oct 25, 1999 at 05:35:31PM +0200, WroBELL wrote:
> > On Mon, 25 Oct 1999, Bernhard Herzog wrote:
> > > If you already have Sketch, it's in Sketch/Base/connector.py. If there's
> > > enough interest, I can make it available separately and write up some
> > > documentation.
> > I think it would a great idea.
>
> Well, talking about signals; can I set up my SIGALRM signal handler function
> to get called when it's timeout is reached and not only when the timeout is
> reached *and* an another gtk event occurs? Using the standard way my
> own signal handler funtion is called only when I click on the window or
> generate any event in a similar way, not at the moment of the alarm.
>
> Christopher
> --
> +-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-: .~. :-=-=-=-=-=-=-=-=-=-=-=-=-=-=-+
> | Christopher Jozsa /V\ Veszprem Linux Users Group |
> | [EMAIL PROTECTED] /( )\ student of IT, Hungary |
> +-=-=-=-=-=-=-=-=-=-=-=-=-=-=--: ^^-^^ :--=-=-=-=-=-=-=-=-=-=-=-=-=-+
> To unsubscribe: echo "unsubscribe" | mail [EMAIL PROTECTED]
>
To unsubscribe: echo "unsubscribe" | mail [EMAIL PROTECTED]
