Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!uunet!sdrc!evgabb From: evgabb@sdrc.UUCP (Rob Gabbard) Newsgroups: comp.windows.x Subject: Re: Problem with Signals Summary: Still more problems ..... Message-ID: <1179@sdrc.UUCP> Date: 8 Mar 90 15:35:00 GMT References: <9002281729.AA02895@wilkins.bcm.tmc.edu> <132399@sun.Eng.Sun.COM> <132645@sun.Eng.Sun.COM> Organization: SDRC, Cincinnati Lines: 19 In article <132645@sun.Eng.Sun.COM>, hvr@kimba.Sun.COM (Heather Rose) writes: > In this example, you should use two processes. One does the 7 hour calculation, > the other handles the window interface. We are using a similar architecture to this model you are descibing. What if your window interface was doing a ray trace into a pixmap that took a longer time to do than your timer interval ? That is where the real danger is. > If you were to use XView for this, you would not even need signal handling Sorry, we're DECWindows/Motif based. -- ________ _________ _______ ________ / _______| | ____ \ | ___ \ / _______| Rob Gabbard (uunet!sdrc!evgabb) | |______ | | \ \ | | \ | | / Technical Development Engineer \_______ \ | | | | | |___/ / | | Structural Dynamics Research Corp. ______| | | |____/ / | ____ \ | \_______ #include |________/ |________/ |_| |_| \________|