nanogui: IPC client/server comm.
Subject:
RE: IPC client/server comm.
From:
"Rob Taylor" ####@####.####
Date:
30 Mar 2000 13:12:53 -0000
Message-Id: <000501bf9a48$4c160ea0$b400a8c0@eventhorizon>
> : Do you think integrating that communication mechanism in nanox would be
> : difficult/long/annoying ? (I know that Morten already contributed shared
> :
> : mem support)
>
> I'm also interested in another option: direct client framebuffer
> mapping. This
> would allow the client process to write the framebuffer directly.
> It would have
> access to shared code and data that would setup the appropriate clip
> regions so that window heirarchies would be maintained...
that would be extra cool ;)
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?
Thanks,
Rob
