On 11/29/05 6:26 PM, David M. Cotter didst favor us with:
>> IIRC, you draw via offscreen. Don't. At least try to fix it first
>> drawing directly and only after you fix it, only then reintroduce
>> your offscreen back if you still need it. Appearance APIs and calls
>> like SetUpControlBackground might work for onscreen drawing only.
>
> wha.. err, ummm, yeah! Hey!! HEY!! That's, like, a good idea!
> Hang on I'll try it....
>
> It works!! Wow. jeez, i feel VERY silly now.
> Somehow I had myself convinced that I must compose my icon (which is
> in fact made of many parts) in an offscreen. But, well, actually,
> there is no reason to do that! I can just compose it right on
> screen.
This is the whole point. You *aren't* composing it "on screen." You *are*
composing it in an offscreen buffer in Mac OS X.
> HAHA! Holdover from my many many years of double buffered
> drawing.
The fact that you can abandon using your own offscreen buffers for this kind
of thing was just discussed here a few days ago in a thread with subject
"GrafPort" in which I said on 11/25:
"Exactly. If indeed this code exists simply to draw the contents of the
window and blit the results to the window, then you can just remove all that
offscreen GWorld code and draw directly to the window in Mac OS X (which is
really means drawing to the window's back buffer). Not only will it simplify
your code considerably, it will reduce memory usage and improve
performance."
Larry
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Carbon-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/carbon-dev/email@hidden
This email sent to email@hidden
