Re: Carbon window compositing
Re: Carbon window compositing
- Subject: Re: Carbon window compositing
- From: William Stewart <email@hidden>
- Date: Tue, 12 Jul 2005 15:01:45 -0700
In light of this (BTW I totally agree with Marc's sentiments), the AU
Hosting app in the SDK is now by default putting up both a composited
(and metal) window as that best points out problems with both
compositing windows and background colours.
We also added an option to AU Lab to make the windows composited, and
I'd recommend developers use this by default.
It is both problematic and limiting that so many views will not deal
with this situation correctly... For instance, the carbon generic
view will (if it is hosted in a composited window), *automatically*
support scrolling if the AU has a large number of parameters. The
code for this is in the SDK, and if you get your view to work with
compositing, then you could inherit this feature for free.
Bill
On 12/07/2005, at 2:54 PM, Marc Poirier wrote:
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
--
mailto:email@hidden
tel: +1 408 974 4056
________________________________________________________________________
__
"Much human ingenuity has gone into finding the ultimate Before.
The current state of knowledge can be summarized thus:
In the beginning, there was nothing, which exploded" - Terry Pratchett
________________________________________________________________________
__
_______________________________________________
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