[B2-devel] Native OS X version 1.0, screen buffer questions

[Nigel P. <ni...@in...>]

Gwenole asked:
> Knowing nothing to CoreGraphics, I have a
> question: how are screen updates managed? I mean is the_buffer
> automatically blitted to the screen by MacOS X?

	Automatically? Well, not really. I have a task that calls
a routine that draws the image in the window. It uses the most
efficient calls there are, but there is something causing a
huge slowdown. I will eventually try using QuartzDebug to see
if there are any obvious problems, but thus far the magical
fix has eluded me.

	I am hoping that a more experienced programmer will be able
to check out the code and work out what I am doing wrong. So far,
no-one had replied to my messages on the macosx-dev mailing list.

	I will also eventually add OpenGL and CGDirectGraphics code.
The latter may be able to do the "automatic blitting" thing.


> Don't you use a back buffer?

	A window has the option of buffered, retained or non-retained.
The latter two are actually slightly slower than buffered, and they
have problems keeping all the other window gadgets drawn, so I am
still using the buffered option.


	Anyone interested in playing with this can edit the compiled
program's interface (using /Developer/Applications/Interface Builder on
the file BasiliskII.app/Contents/Resources/English.lproj/MainMenu.nib).
It should also be possible to add a button to call the benchmark method
( [EmulatorView benchMark] )

--
|Nigel Pearson, ni...@in...  |=93Now the world has gone to =
bed,|
|Telstra iDevelopments, Sydney Australia| Darkness won=92t engulf my =
head,|
|  Office: 9206 3468    Fax:  9212 6329 | I can see by infrared,        =
|
|  Mobile: 0408 664435  Home: 9792 6998 | How I hate the night.=94 =
-Marvin|