Re: [RANT] *Really* getting frustrated now (AU Cocoa UI template STILL not working)
Re: [RANT] *Really* getting frustrated now (AU Cocoa UI template STILL not working)
- Subject: Re: [RANT] *Really* getting frustrated now (AU Cocoa UI template STILL not working)
- From: William Stewart <email@hidden>
- Date: Thu, 7 Aug 2008 19:32:40 -0700
Please do me the courtesy of abusing me with my name spelled
correctly. Its Stewart, not Stuart.
I understand your frustration, and as you would have seen we have
investigated and posted a workaround to your problem.
These questions may seem "banal" to you, but that is really because
you don't understand the complexity of the situation - different
versions of XCode have different versions of the templates that have
different potential issues resolved, and so forth. I think you should
at least do us the courtesy of assuming that the questions we are
asking have some baring on the problem - we endeavour not to ask truly
irrelevent questions. I was not aware that your "favourite colour"
affected the way that XCode templates worked, so I'll certainly follow
up with the engineer concerned and find out how that affects this
problem space; that does indeed seem like an irrelevant question to me.
Bill
On Aug 7, 2008, at 3:59 PM, Walt wrote:
<RANT>
Ditto that. As you correctly observe, I reported the same on this
list several months ago and by response was asked the most banal
questions... "What version of XCode? What version of the OS? What is
your favorite color?" to which I replied "Mac OS X 10.4.n-10.5.n,
XCode 2.5 - 3.n, and electric blue."
Bill Stuart later replied the bug had been fixed. Maybe I'm way off
base here, but perhaps the engineer that fixed it should check it in?
Hopefully one of you kind apple engineers reading this will be
suitably embarrassed by this fiasco and do something about it?
Here's a suggestion. Please take the fixed project, zip it up, and
post it to this list. Your process to get the fix into a release
appears broken... Or could you at least post (or technote) what
needs to be done to fix it? You'd save a bunch of people a lot of
time and frustration.
<RANT^2>
Previous experience suggests that one can not expect all of the core
audio example code to compile, link and run out of the box. It's
hardly a surprise that the templates also have problems. I infer
that life must be really stressful on the CA team. Are you guys that
understaffed? I'm so sorry if that's the case; maybe if you show
your management this thread they'll let you bring on an intern so
you can test the example code/templates from release to release.
Your developers would appreciate your "going the extra mile"...
</RANT^2>
I get paid whether I'm developing useful code for my company, or
wrestling bugs in Apple supplied code. Either way I still get to
eat. I'm only up on this soap box because I prefer the former to the
latter, as I suspect most of my colleagues on this list would
agree... Well, except Stephan; he loves debugging other peoples
code. Kidding!!! :)
</RANT>
-Walt
-----
On Aug 7, 2008, at 3:38 PM, tahome izwah wrote:
Hi all,
so I just completed updating my Xcode installation to 3.1 in order to
get started with a new AudioUnit that I was planning on writing, and
after doing that I had such a bad deja-vu that I really need to share
this with you, having run out of other options at this point.
When I used the AudioUnit with Cocoa View template to create a brand
new AU I realized that after almost a year this thing STILL doesn't
work right. You gotta be kidding me - this bug is so obvious and yet
the AudioUnit Cocoa UI template that is available in Xcode has been
broken since 10.4.0 and apparently noone on the Apple team cares
about
fixing it... yet at the same time you guys recommend using Cocoa to
write UI code for AU plug ins. I'd very much like to do just that,
but
how on earth am I supposed to get this done when even the very
template doesn't work??
Come on - people on this list have already filed a bug report about
it
(FYI this is problem ID #5619322 supposedly filed in late 2007 as far
as I can see from the responses on this list) and quite a few people
on this list have been complaining about it (most notably myself,
Walt, Kevin Dixon, Stephen Bernsee and others - look for the thread
named "[FAQ?] re>x-code template project for AU with cocoa view"),
but
still there is no fix that I am aware of, nor does the latest
devtools
update fix it.
I really don't know what to do at this point so I am asking the
CoreAudio team: are you going to fix the template anytime soon (or at
all), and if not, what's keeping you? Am I (and the rest of the
AudioUnit community) condemned to tweaking the project manually every
single time to make it run until we ultimately die of old age?
Sorry folks, but this is below the expectations I have from using
(and
loving, and endorsing!) Apple products since the 1990s.
Very frustratedly yours,
--th
_______________________________________________
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
_______________________________________________
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