GarageBand moves my AUCarbonView's pane, sneaky style
GarageBand moves my AUCarbonView's pane, sneaky style
- Subject: GarageBand moves my AUCarbonView's pane, sneaky style
- From: Marc Poirier <email@hidden>
- Date: Wed, 24 Mar 2004 18:11:02 -0500 (EST)
Alright, is this legit? After much investigation this afternoon, I have
finally determined that GarageBand has a very peculiar habit with
AUCarbonViews skinnier than 333 pixels...
So, when GB encounters an AUCarbonView with a width of less than 333
pixels, it wants to center that view in the plugin editor window rather
than have it flush against the left edge of the window (as GB does in
other cases). Alright, fine. However, the way that GB goes about
accomplishing definitely at least does not seem okay to me.
First, what GB does not do:
When opening the AUCarbonView via AUCarbonViewCreate, GB does not send the
desired X offset in the inLocation parameter. It sends 0 as the X offset
value, always. (It does send the correct Y offset, though, leaving space
for the presets pop-up area at the top of the window).
What GB does do:
So in order to center the plugin's view, what GB does is, *after*
AUCarbonViewCreate returns, GB then takes the view's parent pane control
and moves it over to the left, where it wants it to be.
I was astounded when I figured this out. I mean, what's the point of
having an X offset argument for AUCarbonViewCreate if you're not going to
use it and then just move the pane behind the AUCarbonView's back later?
So I reported it as a bug rdar://3600256
However, then I realized: Well, if an host does want to center the view,
then how would it do that? After all, it won't know if and how much it
wants to move the view until after it is created and then the host finds
out how wide the view is. Then I cooled off a bit, realizing that this
wasn't as much straight-forward foolishness as I thought it was.
But still, I am wondering if it's considered AU-legit for a host to do
this. I certainly haven't seen anything in the docs mentioning that an
AUCarbonView is supposed to be prepared for this. And mine definitely are
not, and specifically, the plugins that I've worked on that exhibit this
problem are the Pluggo plugins Phase Scope, Spectral Filter, Warble,
Wheat, Space Echo, LFO, and PluggoSync. These all look fux0red in
GarageBand.
So anyway, that's what I'm wondering: are AUCarbonView's supposed to
catch this sort of trickery and accomodate it, or is GarageBand
misbehaving?
thanks,
Marc
_______________________________________________
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.