site_archiver@lists.apple.com Delivered-To: pro-apps-dev@lists.apple.com Jose, At the moment there is no way to identify the frontmost project. There is a bug in about this. -eryk On Oct 23, 2008, at 12:18 AM, Jose A. Guerrero-Colón wrote: Hello everybody, Is there a way to do this? Any ideas? Thanks in advance! Best Jose A. Send Pro-apps-dev mailing list submissions to pro-apps-dev@lists.apple.com To subscribe or unsubscribe via the World Wide Web, visit http://lists.apple.com/mailman/listinfo/pro-apps-dev or, via email, send a message with subject or body 'help' to pro-apps-dev-request@lists.apple.com You can reach the person managing the list at pro-apps-dev-owner@lists.apple.com When replying, please edit your Subject line so it is more specific than "Re: Contents of Pro-apps-dev digest..." Today's Topics: 1. Re: Custom UI parameter in FxGenerator (Paul Schneider) 2. Re: Custom UI parameter in FxGenerator (Darrin Cardani) 3. FCP Apple Event project listing bug (Martin Baker) 4. Re: Custom UI parameter in FxGenerator (Quincey Morris) 5. Valid frameworks (Quincey Morris) 6. Re: FCP Apple Event project listing bug (Helena Ju) 7. Re: Valid frameworks (Paul Schneider) 8. Re: Valid frameworks (Quincey Morris) 9. FCP nested sequence movie (frank) ---------------------------------------------------------------------- Message: 1 Date: Tue, 21 Oct 2008 14:14:38 -0500 From: Paul Schneider <pschneider@apple.com> Subject: Re: Custom UI parameter in FxGenerator To: Quincey Morris <quinceymorris@earthlink.net> Cc: Pro-Apps-Dev <pro-apps-dev@lists.apple.com> Message-ID: <7367A2FC-0525-4BAA-9DF7-6EC21E10C365@apple.com> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Thanks, Quincey. 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. - Paul On Oct 21, 2008, at 1:59 PM, Quincey Morris wrote: On Oct 21, 2008, at 09:23, Darrin Cardani wrote: 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. Done. Filed as #6307617. 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. _______________________________________________ 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 ------------------------------ Message: 2 Date: Tue, 21 Oct 2008 12:17:07 -0700 From: Darrin Cardani <dcardani@apple.com> Subject: Re: Custom UI parameter in FxGenerator To: Quincey Morris <quinceymorris@earthlink.net> Cc: pro-apps-dev@lists.apple.com Message-ID: <E668BDBE-6F03-4E4A-A2D0-9CCA90262D27@apple.com> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes On Oct 21, 2008, at 11:59 AM, Quincey Morris wrote: On Oct 21, 2008, at 09:23, Darrin Cardani wrote: 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. Done. Filed as #6307617. Also filed: #6307731, concerning the memory-corruption bug in the FxFilter template code. Great! Thanks! 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. Darrin -- Darrin Cardani dcardani@apple.com ------------------------------ Message: 3 Date: Tue, 21 Oct 2008 20:45:58 +0100 From: Martin Baker <martin@digital-heaven.co.uk> Subject: FCP Apple Event project listing bug To: Pro-Apps-Dev <pro-apps-dev@lists.apple.com> Message-ID: <3388AB9D-5076-47A7-856D-5647C3316E07@digital-heaven.co.uk> Content-Type: text/plain; charset="us-ascii" Have just filed a bug for this (6307992) but for anyone else that might run into this... Martin Baker www.digital-heaven.co.uk www.videospaceonline.com www.funkycloud.com/lifeshaker ------------------------------------------------------ Digital Heaven Ltd is registered in England and Wales Company registration number: 3628396 Registered address: 55 Lynwood Drive, Worcester Park, Surrey KT4 7AE VAT registration number: GB 736 0989 03 ================= Summary: The FCP Apple Event kFCPGetAllOpenProjects does not return any open projects beyond any unsaved project created in the application. Steps to Reproduce: 1. open a project (A) 2. create a new project but do not save it (B) 3. open a third project (C) 4. open a fourth project (D) 5. using the Apple sample code example for FCP Apple Events, request a list of currently open projects Expected Results: All projects except the unsaved project (B) should be returned in the reply from FCP. Actual Results: Only the first project A is returned. Projects C and D are absent. Regression: Perfectly consistent. The order of creating an unsaved project and opening other projects is crucial. If you launch FCP, create a new unsaved project and then open 10 projects then none of the saved projects will be listed in the reply. The unsaved project is blocking any other projects from being listed. ======================