site_archiver@lists.apple.com Delivered-To: pro-apps-dev@lists.apple.com On Oct 21, 2008, at 11:59 AM, Quincey Morris wrote: On Oct 21, 2008, at 09:23, Darrin Cardani wrote: Done. Filed as #6307617. Great! Thanks! Darrin -- Darrin Cardani dcardani@apple.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... 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. If you'd like these to be fixed, please file them. Otherwise they won't get fixed. This email sent to site_archiver@lists.apple.com