nanogui: IPC client/server comm.


Previous by date: 30 Mar 2000 19:01:00 -0000 Re: IPC client/server comm., Greg Haerr
Next by date: 30 Mar 2000 19:01:00 -0000 Re: client/server protocol speedup, Morten Rolland
Previous in thread: 30 Mar 2000 19:01:00 -0000 Re: IPC client/server comm., Greg Haerr
Next in thread:

Subject: Re: IPC client/server comm.
From: "Greg Haerr" ####@####.####
Date: 30 Mar 2000 19:01:00 -0000
Message-Id: <013001bf9a79$b47610e0$3017dbd0@censoft.com>

: Along these lines, I was just looking at the clipping code just now, and
: just wanted to ask if I was right in thinking that currently the current
: clipping area is stored in a global static, which is manipulated in the
: device level code?


There are two implementations, new and old.  The old version
kept the current clip region in a static MWRECT array.  The
new version keeps a single static pointer to the current clip region,
which dyamically allocated.  A future implementation has every window
structure keep and up-to-date clip region, and then the global goes away.
I chose against this for now since this would mean very excessive memory
usage.

Greg


Previous by date: 30 Mar 2000 19:01:00 -0000 Re: IPC client/server comm., Greg Haerr
Next by date: 30 Mar 2000 19:01:00 -0000 Re: client/server protocol speedup, Morten Rolland
Previous in thread: 30 Mar 2000 19:01:00 -0000 Re: IPC client/server comm., Greg Haerr
Next in thread:


Powered by ezmlm-browse 0.20.