On Aug 1, 2008, at 4:16 AM, Chris Wood wrote:
Perhaps somebody at Apple could clarify that a bit? Should private
patches be avoided for 'serious release' type applications?
This spurred some discussion amongst ourselves and the answer is very
stark.
We strongly warn developers not to use private patches. Undocumented
or private functionality in QC will not be supported, is subject to
change without notice and at any time, and should not be relied upon
or used in applications intended for distribution.
!!
Allan
___________
Allan Schaffer
Graphics Evangelist
Worldwide Developer Relations
On Aug 1, 2008, at 4:16 AM, Chris Wood wrote:
Forgot the 'reply to all' button yet again :/ Reply from earlier,
with request for comment from somebody at apple if at all possible:
It should just work. I've used them without issue in applications in
the past without any issues.
The thing you should be aware of though is that these patches are
presumably private for a reason. There could be issues of some kind
with them (although I've not come across any personally), or apple
could change the patches in some way in a future OS update, breaking
your application.
Perhaps somebody at Apple could clarify that a bit? Should private
patches be avoided for 'serious release' type applications?
Chris Wood
2008/8/1 Steven Sokulski <[EMAIL PROTECTED]>
I have enabled the added patches in Leopard and am wondering what
will happen if I use a private patch in a composition that is
included in an application. Is there something I need to do when
building the app in XCode to make the patch usable?
Thanks in advance.
Steven
_______________________________________________
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]
