Re: Custom UI parameter in FxGenerator
site_archiver@lists.apple.com Delivered-To: pro-apps-dev@lists.apple.com Thanks, Quincey. - Paul On Oct 21, 2008, at 1:59 PM, Quincey Morris wrote: On Oct 21, 2008, at 09:23, Darrin Cardani wrote: Done. Filed as #6307617. _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/pschneider%40apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.ap... Everyone, please file bugs for any problems you find with the FxPlug documentation and sample code at bugreport.apple.com. Don't assume that a problem is so obvious that we must already know about it; duplicate bug reports are easy to screen for, and let us know that multiple people are being affected by an issue. Reporting issues to us over email is good, but filing bugs using the website is better. Emails can easily fall through the cracks, but bug reports go into a database where they will haunt us forever. This sounds like a bug in Motion. It should be working the same as with a filter. If you could file a bug report, I'd appreciate it. Also filed: #6307731, concerning the memory-corruption bug in the FxFilter template code. Not filed: report concerning the bug in the FxGenerator template code, because it appears to be harmless. (It uses [FxBitmap dataPtrForPositionX:Y:] on bitmaps whose component depth is not 8, although the documentation says this is not allowed. I guess it works because X is 0 in this case, so the pointer depends only on Y and rowBytes. Or maybe the documentation is wrong.) Not filed: report concerning the FxHostCapabilities documentation, which appears to say that the 'supportsXXX' methods return NO if 'XXX' is supported. Not filed: report concerning the FxTimingAPI documentation, which describes a 'inputTimeForParmId:forEffect:fromTimelineTime:' method that doesn't exist. This email sent to pschneider@apple.com This email sent to site_archiver@lists.apple.com
participants (1)
-
Paul Schneider