Re: select(), epoll(), etc... in GUI?
- From: takeout <user@xxxxxxxxxxx>
- Date: Mon, 24 Dec 2007 11:48:16 -0700
Good info, thanks people. I have found that Xt provides XtAddInput(), GTK+
provides IO Channels, ...and Qt provides QSocketNotify thingy(?)
Still trying to understand the signals and how you can safely perform operations
in them. Ahha, a least for a single threaded process, the signal handler
function will be 'atomic' right? It will not be itself interrupted by your main
process code. So you could define some global variables that the signal handler
can write to, and that should be read only by the rest of the process. I don't
think I could safely modify a GUI event queue from a signal handler though.
I think GTK IO Channels will solve my specific problem since im using wxGTK.
I'll try that.
--
_______________
hello friend!
i tend to ignore the following kinds of replies: top-bottom-middle posting,
grammar, spelling, read the manual you %#!, search google you !@%... thank you.
.
- Follow-Ups:
- Re: understanding of signal handling details
- From: Markus Elfring
- Re: understanding of signal handling details
- References:
- select(), epoll(), etc... in GUI?
- From: takeout
- Re: select(), epoll(), etc... in GUI?
- From: Jan Kandziora
- Re: select(), epoll(), etc... in GUI?
- From: Rainer Weikusat
- select(), epoll(), etc... in GUI?
- Prev by Date: Re: check if memory is accessible
- Next by Date: fsync
- Previous by thread: Re: select(), epoll(), etc... in GUI?
- Next by thread: Re: understanding of signal handling details
- Index(es):
Relevant Pages
|
|