home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.next.programmer
- Path: sparky!uunet!oceania!jeff
- From: avsoft!jeff (Jeff Roberts)
- Subject: signals and the appkit
- Message-ID: <Bs4G4M.19M@oceania.com>
- Keywords: sigvec, event loop
- Sender: jeff@oceania.com (Jeff Roberts)
- Organization: Oceania Health Care Systems
- Date: Tue, 28 Jul 1992 23:05:08 GMT
- Lines: 35
-
- We've been having a bit of difficulty with the interaction of the UNIX
- signal facilities and appkit based applications. Any help would be
- greatly apprecatiated.
-
- We are using sigvec to set a handler to catch SIGCHLD. (wait?(2) is no
- good as this application has other tasks to perform.) Since the handler's
- stack is finite, we want to post an event to notify the application and
- that there is work to be done and get off the stack. The handler is
- getting called ok but we can't seem to find a way to let the application
- know that it should re-run the event loop. timer events, delayed
- performs, etc do nothing. If you take on too ambitious a task in the
- signal handler itself, like sending appkit objects messages, the
- application seems to get hung in the event loop and we get an infinite
- wait cursor.(This condition applies to sending the activateSelf: message
- to NXApp) I'm not sure why. My guess would be that we've over ran the
- signal handler stack frame???
-
- Other facts:
- 1. By design, at the time the signal handler is called, this application
- has no screen realestate; no icon miniwindow, no nothing. All windows
- have been ordered out.
-
- 2. any events we post in the handler appear to be getting queued up. if
- we leave a window exposed and mouse down on that window we get a flood of
- all of the queued up timer events, etc.
-
- This sounds strange, and believe me it is. I'm a pretty familiar with
- UNIX systems in general but i must admit i'm left without a clue on this.
- Any ideas?
-
- J Roberts
- jeff@oceania.com
-
-
-
-