Re: Custom parameters with kFxParameterFlag_CUSTOM_UI
site_archiver@lists.apple.com Delivered-To: pro-apps-dev@lists.apple.com User-agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.18) Gecko/20110616 Lightning/1.0b2 Thunderbird/3.1.11 Yes, if you want features added or bugs fixed, you absolutely must report them officially using bugreport.apple.com <http://bugreport.apple.com>, or whatever other bug reporting mechanisms you usually use. I should say that many of us did advocate for custom controls in Final Cut Pro X. There were, of course, time and resource constraints to deal with. But there was also a lot of resistance from management because of the way that custom controls and custom windows tend to be used. When they looked at plug-ins with custom controls, a lot of what stood out to them was gaudy logos in the inspectors, and frankly it really turned them off. Obviously, there are good and bad ways to use custom controls, but we had a hard time convincing management how important they are to usability because of the downsides. _______________________________________________ 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... On 6/29/2011 11:29 AM, Darrin Cardani wrote: Well, management knows best. But I cringe at the thought of using a checkbox or popup to do what a simple NSButton could do in FCP. This email sent to site_archiver@lists.apple.com
participants (1)
-
Paul Miller