October 2008 - Pro-apps-dev

Valid frameworks
by Quincey Morris 21 Oct '08

21 Oct '08

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=mO+6X62pr8vcVwJJcvauII5b85Pe8kLppph1p9OjuRpci1mX7QkH3ZWZ2qKW/DCu; h=Received:Message-Id:From:To:Content-Type:Content-Transfer-Encoding:Mime-Version:Subject:Date:X-Mailer:X-ELNK-Trace:X-Originating-IP; Any guidance about deciding what to use and what avoid would be welcome. _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… I'm a bit confused about which frameworks an FxPlug is allowed to link against. The template Xcode FxPlug projects all import <Foundation/ Foundation.h> in the plug-in header file, suggesting that plug-ins are not expected to use AppKit. However, the project itself includes the AppKit framework -- as a set of headers AND as a framework to link against in the predefined target. I'm assuming there's plenty of stuff in AppKit that it's NOT safe to use (anything to do with NSApplication, for example), but the question is what (if anything) is safe to use. So far, open and save panels seem to work, as does the NSBundle class. Views work, for custom UI parameters, and alerts seem to be OK, but what about additional windows in general? What about bindings? I would like to use NSWorkspace, but I've no idea whether it needs support from the host application or not. This email sent to site_archiver(a)lists.apple.com

1 0

Re: Custom UI parameter in FxGenerator
by Quincey Morris 21 Oct '08

21 Oct '08

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=Zj45UQW+kPHjjxyrmspPTkMZh5SN80AzMc2zW4HllSUXA+Ghw/BNvqdt5cahUefv; h=Received:Message-Id:From:To:In-Reply-To:Content-Type:Content-Transfer-Encoding:Mime-Version:Subject:Date:References:X-Mailer:X-ELNK-Trace:X-Originating-IP; On Oct 21, 2008, at 12:14, Paul Schneider wrote: _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… 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. Yes, yes, I know. It's just that whining on the list instead is so much easier, and strangely satisfying. This email sent to site_archiver(a)lists.apple.com

1 0

FCP Apple Event project listing bug
by Martin Baker 21 Oct '08

21 Oct '08

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:mime-version:to:message-id :content-type:from:subject:date:x-mailer:sender; bh=9C4TCpk9Pq6GWzGWah58N4zdiN9gf9XLATY3pi11ifI=; b=xFeA/VqIXFcJ3Q4efRrPg2WY+Obu1eRKC40aRdxktkoaS2cnshUBX5XeL3rNHk4RnE PfeEXVPHFWbfA8q0gmMK6zz8lmoKUFxQy6YaaAzoiOBoduCfr3jy25Jr7/WgxfEnmP78 uC5L+RhTw7apVVHeetb/GC7QW0rRgYE6c+ePg= Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:to:message-id:content-type:from:subject:date:x-mailer :sender; b=Tcc69d3aF88T/lqbHCDf52JbidU4wAO7hWPTHT4vf59ZfM62jm1pnPdoDBqmUDPLge mC+ywl15tKfe2g11wFW40h8yeP/s3NI/eNw3hGtfoSRuvDycBZUU79otWNixje8g5otu svQiOkU1ZcuwkKflW9spkUE7ozBI1dnlTLzKU= _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Custom UI parameter in FxGenerator
by Darrin Cardani 21 Oct '08

21 Oct '08

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)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(a)apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… 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(a)lists.apple.com

1 0

Re: Custom UI parameter in FxGenerator
by Paul Schneider 21 Oct '08

21 Oct '08

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)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(a)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(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… 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(a)apple.com This email sent to site_archiver(a)lists.apple.com

1 0

Re: Custom UI parameter in FxGenerator
by Quincey Morris 21 Oct '08

21 Oct '08

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=l4MZwfFlBWOIYQS5b0tCxzp8tskP1sujdmYHtqckxOTcTGgWk+iTFSCTF47Rtv4g; h=Received:Message-Id:From:To:In-Reply-To:Content-Type:Content-Transfer-Encoding:Mime-Version:Subject:Date:References:X-Mailer:X-ELNK-Trace:X-Originating-IP; 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(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… 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 site_archiver(a)lists.apple.com

1 0

Re: Custom UI parameter in FxGenerator
by Darrin Cardani 21 Oct '08

21 Oct '08

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com On Oct 20, 2008, at 9:55 PM, Quincey Morris wrote: Darrin -- Darrin Cardani dcardani(a)apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… I've tried to add a custom UI parameter to a generator plug-in. The associated custom view simply contains a button. In FCP, the view shows up in the Controls tab of the Viewer. In Motion, the view shows up in the Inspector, but in the HUD for the plug-in the parameter shows as a (malfunctioning) slider instead. If I replace my custom UI parameter setup with the code from the Options Dialog FxPlug example, I get the same results, with the slider in the HUD. The Options Dialog example itself works, but it's a filter, not a generator. I tried writing a filter with the custom UI parameter setup from my generator, and it works correctly in the HUD display. I can't think of any other differences, so I'm wondering if this is a bug in generators only. Does anyone know anything about this, or can anyone suggest some further testing to find out why the view is not displaying in the HUD? BTW, in Motion 'createViewForParm:' isn't being called for the HUD. It's called for the first time when it's needed for the inspector. In FCP, it's called once during startup, and then again when it's needed for the Controls tab. Quincey, 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. This email sent to site_archiver(a)lists.apple.com

1 0

finding out the version of Final Cut Pro running on system
by Tommy Schell 21 Oct '08

21 Oct '08

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Hi, Thanks Tommy Schell _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… I'm using Apple Events to interact with Final Cut Pro, is there a way to query Final Cut Pro or some other way to find out the current version of FCP? As different versions can handle different events. This email sent to site_archiver(a)lists.apple.com

1 0

Re: finding out the version of Final Cut Pro running on system
by Martin Baker 21 Oct '08

21 Oct '08

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:mime-version:in-reply-to :references:content-type:message-id:from:subject:date:to:x-mailer :sender; bh=nTGOZ4DzfLid3IBkElA/G9wMZTATNXMvsPzRGIsg/RQ=; b=tv57D+OpKguENVBbsyic8QkbOW3/VZbDmr/nE9KKTf1qbjLJ/k8pOA1k0a2VLWpaAJ fDXvUhsQQkcilWgPRbgO4NfzRq0p0pk9GFauXfVzBJje2tGeTgR8QZxi2nSQrnbL9oZJ DGA63k9S9eirIqniiNzh5qqCeWm6iqOQTwFQI= Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:content-type:message-id:from :subject:date:to:x-mailer:sender; b=c8bPzj2Qfk0I2TI6/0qAVJT+M3jr8aA5hkvyHgElshH+mVY7UivmtiSSmXEGPxjiiW lB+n6ZuN3sVOhb8Fc5mp1M2yWk59WX4rhADMed3eJuPcx6Zv8UHnDqhzqFWfsDXTsTDL AUWJQpLbmx6S4RRchX939A8N8PDsUioI9ILFc= _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Custom UI parameter in FxGenerator
by Kristian Harms 21 Oct '08

21 Oct '08

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Hi Quincey, Regards, Kristian Harms Den 21. okt.. 2008 kl. 06.55 skrev Quincey Morris: I've tried to add a custom UI parameter to a generator plug-in. The associated custom view simply contains a button. In FCP, the view shows up in the Controls tab of the Viewer. In Motion, the view shows up in the Inspector, but in the HUD for the plug-in the parameter shows as a (malfunctioning) slider instead. If I replace my custom UI parameter setup with the code from the Options Dialog FxPlug example, I get the same results, with the slider in the HUD. The Options Dialog example itself works, but it's a filter, not a generator. I tried writing a filter with the custom UI parameter setup from my generator, and it works correctly in the HUD display. I can't think of any other differences, so I'm wondering if this is a bug in generators only. Does anyone know anything about this, or can anyone suggest some further testing to find out why the view is not displaying in the HUD? BTW, in Motion 'createViewForParm:' isn't being called for the HUD. It's called for the first time when it's needed for the inspector. In FCP, it's called once during startup, and then again when it's needed for the Controls tab. _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/kha%40vizrt.com This email sent to kha(a)vizrt.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… We're in much the same situation with a custom view parameter in an FxGenerator. I wasn't aware that it worked in filters, but to prevent the parameter from appearing in the HUD, you can add the kFxParameterFlag_DONT_DISPLAY_IN_DASHBOARD flag to the parameter when you add it. This email sent to site_archiver(a)lists.apple.com

1 0