Sorry about that Milton. I totally respect bringing up valid bug points, and my statement was in fact a bit in jest, as Vade has asserted. At the same time, in reading your dialogue, it was very clear that:
#1: You are obviously largely unfamiliar with Quartz Composer, and are trying to design a plug-in without being aware of, or concerned about user expectation, even after this was kindly pointed out to you. #2: You already had your mind made up about your answers before posting to list, and were making a cyclical and largely pointless argument, while wrangling people into giving you valid solutions to your problem, simply because you were locked into a mindset of not wanting to change your approach. I feel sorry for the people that wasted their time trying to help you. #3: I don't really care about your response, as I don't want to get into the same kind of pointless cycle that your thread devolved into. #4: Search engine results reveal a consistent pattern of you asking questions, ignoring answers, and making a habit of making hyperbolic statements, such as "getting Steve-d". That kind of attitude only undermines any possible validity that your argument may have. So, that's what I mean by "pulling a Milton". If you don't like it, I would suggest that you take a step back and think about how your dialogue actually would strike someone else. Regardless of whatever you think, if it strikes people that way, then there must be a reason, and it certainly isn't out of a personal desire to "defend" QC. *Back OT:* Thanks for the suggestions and clarifications. There are some pretty valid workaround mentioned here, enough so that I can get what I want to have work, to work. I would like to see the Constant Color "not do this", but it's not a deal breaker. Best regards, George Toledo On Tue, Oct 27, 2009 at 2:45 PM, Milton Aupperle <[email protected]>wrote: > If by "Pulling a Milton" you mean filing bug reports and publicly alerting > others to grievous memory, thread and object leaks in Apple examples code > that will affect your existing plugins that are built off them, then I think > we should all be "Pulling a Milton". > > The way bug reporting works as far as fixes go at Apple is that the more > reports of the same bug affecting people they receive, the higher up the > priority ladder it is. So if multiple developers file bugs on the same > issue, then it likely gets fixed. If one person files it, they are far less > likely to even bother with it. Thats one of the reason I raised the issues > here. > > And when I'm done this project, I'll be filing multiple bug and enhancement > request clearly indicating what Apple need to change to make this workable > for 3rd part hardware developers, especially since most 3rd party QuickTime > Video drivers and components will not work under 64 bit Apps (architecture > is 32 bit only). > > Given how hostile I feel the list is to criticism of QC, I won't bother > posting them here. > > Milton J. Aupperle > President > ASC - Aupperle Services and Contracting > Mac Software (Drivers, Components and Application) Specialist > #1106 - 428 Chaparral Ravine View SE. > Calgary Alberta T2X 0N2 > 1-(403)-453-1624 > *[email protected]*** <[email protected]> > www.outcastsoft.com > > > On 27-Oct-09, at 11:09 AM, George Toledo wrote: > > Btw, didn't mean to "pull a Milton". > > Best regards :), > > George Toledo > > > > > > > >
_______________________________________________ Do not post admin requests to the list. They will be ignored. Quartzcomposer-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/quartzcomposer-dev/archive%40mail-archive.com This email sent to [email protected]
