Re: [Alephmodular-devel] Drawsprockets?
Status: Pre-Alpha
Brought to you by:
brefin
From: Br'fin <br...@ma...> - 2003-03-11 22:04:14
|
*Laugh* What a splendid concept. Seems a couple Carbon calls... Some corresponding application services calls, also with carbon apis And a whole bunch of CGDirectDisplay and CGDirectPalette APIs also in application services. -Jeremy Parsons On Tuesday, March 11, 2003, at 04:22 PM, Alexander Strange wrote: > > On Tuesday, March 11, 2003, at 01:57 AM, Br'fin wrote: > >> Is there yet a more appropriate API than DrawSprockets for going >> right to the display hardware of MacOS X? Right now CDisplay is very >> centered towards the way AlephModular currently uses a single back >> buffer that is always getting copied forward (A window back buffer >> and appropriate flush to display calls) I'm sure this will turn up >> cases of flicker (Places where info needs to be updated on both >> buffers not getting updated properly) Hooking it up with >> DisplaySprokects should help flush out those areas in need of >> improvement. But I really don't know if DrawSprockets is the Apple >> recommended way of going about this anymore. >> >> -Jeremy Parsons > > Well, I assume a "more appropriate" API would be whatever > DrawSprockets uses. > Run 'otool -LHV > /System/Library/Frameworks/DrawSprocket.framework/DrawSprocket' and > see. |