home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!cs.utexas.edu!rutgers!uwvax!uchinews!msuinfo!tardis!adc
- From: adc@tardis.msu.edu (Alan D. Cabrera)
- Newsgroups: comp.windows.open-look
- Subject: Re: Xview: Drawing to the user interface from a
- Message-ID: <1992Aug23.170134.24711@msuinfo.cl.msu.edu>
- Date: 23 Aug 92 17:01:34 GMT
- References: <l9e40bINNth@saltillo.cs.utexas.edu>
- Sender: news@msuinfo.cl.msu.edu
- Reply-To: adc@tardis.msu.edu
- Organization: Michigan State University
- Lines: 26
-
- In article l9e40bINNth@saltillo.cs.utexas.edu, julian@cs.utexas.edu (Dun Julian Wong) writes:
- > I am writing an X-Window application using Xview. There are two processes in
- > the program that are run concurrently. One of the process is the user
- > interface, which is controled by xv_main_loop(). The other is my main() program.
- >
-
- I would think that having two processes conversing with X, even with
- the "correct" parameters, would be very confusing to the underlying
- code, hence the core dump.
-
- I would rather ask the question, why split your application into two
- processes in such a way that BOTH need to do X window calls? This
- indicates to me muddy thinking and the design of your program needs to
- be thought out.
-
- Of course, I could be wrong; if I had a nickle for ever time I was
- wrong... I'm very interested in hearing about your application as I
- still believe that you have improperly partitioned your problem.
-
-
- ---
- Alan Cabrera internet: adc@tardis.cl.msu.edu
- Computer Laboratory phone: (517) 353-3027
- Michigan State University fax: (517) 353-9847
- 514 Computer Center bitnet: CABRERA@MSU
- East Lansing, MI 48824
-