AudioUnits and compositing windows (was AudioUnits and Cocoa UI)
AudioUnits and compositing windows (was AudioUnits and Cocoa UI)
- Subject: AudioUnits and compositing windows (was AudioUnits and Cocoa UI)
- From: Airy André <email@hidden>
- Date: Tue, 18 Mar 2003 13:45:34 +0100
Le mardi, 18 mars 2003, ` 13:35 Europe/Paris, Urs Heckmann a icrit :
Am Dienstag, 18.03.03, um 12:38 Uhr (Europe/Berlin) schrieb Airy Andri:
Le mardi, 18 mars 2003, ` 09:07 Europe/Paris, Urs Heckmann a icrit :
Reg. Logic and support by apps, I see that we already have that
pending issue in respect of Compositing Windows. I hope we can get
some example code or an update of AUCarbonViewBase for that, too. (I
think it's about removing EmbedControl and using HIView APIs
instead). That way, support for nested Controls would be nice as
well...
You can use AUCarbonViewBase for compositing windows. It just work.
Uh-hu, I always thought it's the EmbedControl in AUBase that screws it
up...
In my SDK, in AUCarbonViewBase, I have :
if (attributes & kWindowCompositingAttribute) {
verify_noerr(::HIViewAddSubview(inParentControl, mCarbonPane));
mXOffset = 0;
mYOffset = 0;
}
else {
verify_noerr(::EmbedControl(mCarbonPane, inParentControl));
mXOffset = inLocation.x;
mYOffset = inLocation.y;
}
... is there already an example host that does Compositing Windows?
Shouldn't AUHosting have it?
Just make a copy of SynthTest, open the nib, select the window for the
AU GUI, click on "compositing", save.
You've make one.
Our AUGUIFramework support both compositing and non compositing
windows, and is entirely built around HIViews and nested controls...
In fact, half of our code is for supporting non compositing windows...
So you already have sample code available ;-)
Yeah, I should have a look at that. But on the other hand, if you read
CAUGui's license, it urges people who get it to work with Compositing
Windows to give back that code (the only true limitation in my license
8-), so I have a very small hope that I won't have to bother with that
too much...
One thing that I don't like on the idea of multiple windows is the
waste of screen estate. My beta testers voted for Tabbed Panes and
dynamic changes instead of multiple windows. So this is where I go.
I agree with that, and we also recently went to the multipane way.
Cool. Do you have a file loader class there? - I'll check it out.
What do you call a file loader class ?
Our new multipane is automatically built from nib files, and
automatically switch its content according to its value (and can be
bound to a AU parameter...). No user code needed at all :-)
Is it that you are talking about (loading its content from nib files) ?
Cheers,
;) Urs
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.