Re: Providing a font menu
Re: Providing a font menu
- Subject: Re: Providing a font menu
- From: Martin Baker <email@hidden>
- Date: Fri, 12 Aug 2011 22:06:54 +0100
Thanks for the suggestions Darrin but I don't think the user experience would be good enough. Users who are familiar with the font menus on title templates would expect the font menu of a text generator to work in the same way.
Given the sensitivity about ugly UI design, it seems ironic that we would have to resort to non-standard workarounds to create a font menu in FCPX. It's frustrating that what we could do with FxScript isn't possible with FxPlug 2. I never imagined for a moment, that would be the case.
Off to file that feature request now!
Martin Baker
www.digital-heaven.co.uk
www.twitter.com/digitalheaven
www.videospaceonline.com
www.finalcutters.com
------------------------------------------------------
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
On 12 Aug 2011, at 17:56, Darrin Cardani wrote:
>
> On Aug 10, 2011, at 3:37 PM, Martin Baker wrote:
>
>> From what I've read in past posts, it seems this is not possible but I want to make sure I haven't missed something.
>>
>> - If our FxPlug needed to present a font menu to the user then we should do it using a customUI control. This is because the parameter ID cannot guaranteed to be the same in the situation that a project is moved between systems or a new font has been installed. So we would be using NSCoding to create a unique id to a particular font.
>> - CustomUI parameters cannot be published from Motion to FCPX.
>> - So we can't write an FxPlug that needs a font menu and have it work in FCPX.
>
> I wouldn't put it quite like that. You can't have a custom UI font menu published from Motion to FCPX, that much is true. However, you do have some options. Probably the easiest is to implement a simple OSC that doesn't draw anything but allows the user to press a key combo to bring up the system "Fonts" panel. It's not as discoverable as other methods, though. You could also have a fixed-list of fonts you know will be on all systems. That's limiting and kind of lame, though. You could have an OSC button that when clicked displays the system "Fonts" panel, or use some other regular UI control in an odd way to do it. I agree none of these are ideal, but they are at least workable.
>
> Darrin
> --
> Darrin Cardani
> email@hidden
>
>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Pro-apps-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden