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]
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]
