Re: Carbon AudioUnitView in an NSWindow
Re: Carbon AudioUnitView in an NSWindow
- Subject: Re: Carbon AudioUnitView in an NSWindow
- From: William Stewart <email@hidden>
- Date: Fri, 10 Feb 2006 15:08:50 -0800
On 10/02/2006, at 3:01 PM, Dominic Feira wrote:
Yes I have.
<snip>
Disjoint Activation:
Except in the case of non-activating panels, only one window can be
active in an application at a given time. This looks odd because
clicking on the owning Cocoa window will deactive UI in the Carbon
window, and clicking on the Carbon window will deactivate the UI in
its owning Cocoa window. We have avoided part of the problem by
making our panel non-activating. While we never lose activation in
the toolbar, we do lose the activated state in the Carbon window.
This is still being investigated.
.
.
< end of document; last modified 4 Dec, 2003 >
<snip>
The solution listed in there is to use floating panels, which is
what Garage Band does.
The "solution" is actually to use Panels - whether they are floating
or not is an option that doesn't affect this behaviour. In AUL you
have an option to use floating or not.
Not sure why I asked what Garage Band does.... Anyway, I'd like to
do the same thing, but with a regular document window.
We couldn't get this to work - this is, as described above, still an
area that is under investigation.
A floating window is not always an appropriate solution. Has this
been updated at all since 2003?
What I want to do is pin the Carbon window to a Document window and
have all of the activation handled properly. The activation is the
current problem. They activate independent of each other and as
noted in the document looks silly.
Yes, as described.
Bill
Dominic Feira / Code Monkey / Ambrosia Software, Inc.
On Feb 10, 2006, at 5:44 PM, William Stewart wrote:
These details should be covered in the document that Stefan listed
below. Have you looked through this? If there are things missing
from here, we will add them.
Bill
On 10/02/2006, at 1:41 PM, Dominic Feira wrote:
Okay. I'll just accept that using multiple windows is the best
way to handle this situation. The job of reconciling the Carbon
and Cocoa world's was not looking like a fun task. I just wanted
to ask to be sure. Thanks for the help. Now on to new questions.
Once I have the Carbon window pinned to the Cocoa window with
addChildChildWindow, the 2 windows still activate separately.
How do I get them to behave as one window for activation?
Are you using window groups in Garage Band? I tried to use a
window group already, but it doesn't appear to work. I add both
windows to the same group, but they do not drag or activate
together. I don't see a Cocoa way to accomplish this.
Also, how do you get the parent window to resize when the child
window does? I guess what I'm running into here is my
unfamiliarity with Carbon. I'll have to take this to that list
soon.
Thanks again.
P.S. This is cross-posted t to the core-audio list for
completeness, even though it really isn't a CA issue anymore.
Dominic Feira / Code Monkey / Ambrosia Software
On Feb 10, 2006, at 6:18 AM, Stefan Gretscher wrote:
Hi Dominic,
we're hosting Carbon AU views in GarageBand pretty much like
described in the CoreAudio SDK:
/Developer/Examples/CoreAudio/Documentation/AudioUnits/
CarbonViewCocoaWindow.rtfd
This has been working pretty good for us, so what's the "obvious
drawbacks" you're seeing with this parent/child approach?
Best,
Stefan
Am 10.02.2006 um 02:13 schrieb Dominic Feira:
I need to display Carbon AudioUnitView's in a Cocoa app. So
far, I have been able to insert the Carbon view into the
NSWindow, but it is drawn behind all of the Cocoa views and
doesn't receive any events.
I guess it is a 2 part problem then.
1. Is it possible to get the Carbon view to draw in front of
the NSViews?
2. How do I get the Carbon view to respond to events?
If anybody has experience embedding Carbon controls inside of
an NSWindow I'd appreciate any suggestions or insight.
I have read the recommended approach in /Developer that says to
create a window and use parent/child windows to pin the Carbon
window containing the carbon AudioUnitView to the parent
NSWindow. This approach obviously has drawbacks. So, I'm
researching any other possible solutions to this problem.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40apple.com
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
_____________________________________________________________________
_____
--
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