Tim Dijkstra schrieb: > On Tue, 27 Mar 2007 12:51:54 +0200 > Denis Oliver Kropp <[EMAIL PROTECTED]> wrote: >> Now I see. Yes, you need to keep the keyboard thread alive as well >> if you depend on it to resume. > > That is to bad. We can only have one thread during the freeze. If I > could just read the keyboard state, without input buffer and the like, > that would be enough for me. There is no loop hole for that?
Two possible solutions: - use async io with signals on the main thread - export a function in the input driver, called in suspend mode to check/wait for input Both is not very nice, but I'd go for the second option. Signals are always bad, e.g. for non-EINTR aware code. -- Best regards, Denis Oliver Kropp .------------------------------------------. | DirectFB - Hardware accelerated graphics | | http://www.directfb.org/ | "------------------------------------------" _______________________________________________ directfb-dev mailing list [email protected] http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
