Re: Carbon window compositing
Re: Carbon window compositing
- Subject: Re: Carbon window compositing
- From: Marc Poirier <email@hidden>
- Date: Tue, 12 Jul 2005 17:54:01 -0400 (EDT)
On Fri, 8 Jul 2005, seb_plogue wrote:
I've been thinking about posting this for a while so might as well
do it now while we're on the subject.
Luke Bellandi wrote:
Compositing is set on a Carbon window at the time it's created. It's at
the Audio Unit host's discretion as to whether or not the window will be
composited: views don't have any control over that. Consequently, views
should be prepared to draw correctly in both composited and non-composited
Carbon windows.
Last time I tried having composite windows I had problems with
some plug-ins not drawing correctly (I admit it's been a few months
so maybe they all work now). So as long as these plug-ins are floating
around that would stop hosts to give composite windows to plug-ins.
Any host using composite windows only yet?
Shouldn't there be something in the plist of the component to
specify a plug-in prefers composite or not so those not publishing
it would get a non-composite window?
I agree that it's definitely a problem that so many AUCarbonViews fail to
work in compositing windows (for what it's worth, though, all of the AUs
that I've developed do and have for a long time), however an AU Component
doesn't have any connection to a plist (or bundle, for that matter), so
this won't work. There's no way to go from Component or ComponentInstance
to CFBundleRef.
Marc
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden