Re: linked Cocoa-Carbon windows for AUCarbonViews
Re: linked Cocoa-Carbon windows for AUCarbonViews
- Subject: Re: linked Cocoa-Carbon windows for AUCarbonViews
- From: Stefan Gretscher <email@hidden>
- Date: Tue, 27 Sep 2005 20:50:04 +0200
Marc,
I don't understand why you want to modify the entire window instead of
using transparency in your AU view only?
This should be ok with the spec and will save you from messing up any
host that adds its own controls to the same window that the AU lives
in.
Best,
Stefan
Am 27.09.2005 um 20:27 schrieb Marc Poirier:
On Sep 27, 2005, at 2:05 PM, William Stewart wrote:
On 27/09/2005, at 7:56 AM, Stefan Gretscher wrote:
Hi Marc,
this is something I've been considering as well recently.
I don't think that an AU should access anything outside the view
it's been assigned to, it certainly should not touch any grouped
windows.
How about instead changing the hosts apps so that they set those
areas of their grouped windows to full transparency which are placed
underneath the actual AU UI?
What if the AU's UI is only taking up *part* of the window?
Yes, I realize that that's possible (I've been doing most of my basic
testing in AudioUnitHosting). Again, though, no biggie; if you change
the transparency and then don't like the result, then you just turn
the transparency right back down. The way I've currently implemented
it, when you choose "set window transparency" from the AU's contextual
menu, a floating window pops open with a slider control, and the
slider control does live updating so you see the changes as you slide
it, and so you simply slide it back down to 0 if you don't like the
results. I think it's better than nothing, and in no way worse than
nothing. :)
For non-transparent AU UIs, this makes no difference at all because
the AU completely hides the area in question, and for transparent AU
UIs it would work as expected.
What do you think?
Its really not the AU's window - I think this is a great feature
request for host apps to provide their users.
Oh, I know it's wrong, and I'm usually one of the first to say you
shouldn't do this sort of thing if it's wrong... ;-) But really I
think it's handy and I doubt that all or most hosts will offer it as a
feature, and it's so totally benign, so I'd rather still see it as an
option in my plugs. But yet, even better yet to have it available for
all plugins.
Actually, what I have been meaning to do is file an enhancement
request at Apple Radar for this feature at the OS-level, to provide a
user interface to change the transparency of any windows. That's
where I think the feature belongs, personally. I will try to remember
to file that sometime soon...
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