Re: FCP ui problem
Re: FCP ui problem
- Subject: Re: FCP ui problem
- From: Eberhard Ammelt <email@hidden>
- Date: Tue, 18 Jan 2011 19:03:10 +0100
Sorry, I mixed something. It's not a popup menu from a custom parameter but a standard menu parameter, the menu of which appears in the export dialog.
The plugin has several custom parameters, one uses a popup menu as well. They all load their resources via "loadNibNamed". Some of the parameters control visibility and/or enabling state of others. The parameter in question is not controlled by others but controls another one, which is custom.
Apologies for the confusion,
Eberhard
> OK, so for your custom parameter, you're either building the view hierarchy in code or loading it from a nib, right? Are your popup button's items set once, either when built in code or loaded from the nib, or do you change them over time in reaction to other parameter value changes, for example? Just wondering about the latter case and if somehow you could be grabbing the wrong popup button. (I was thinking if you were using something like -viewWithTag:.)
>
> steve
>
>
> On Jan 18, 2011, at 7:32 AM, Eberhard Ammelt wrote:
>
>> Hello Steve,
>>
>> the plugin uses only nib files to store resources.
>>
>> Thanks anyway,
>> Eberhard
>>
>>> The only reason I can think of offhand is that QuickTime and your plugin are storing your UI elements in resource files instead of nibs, and that your popup button has the same resource ID as QuickTime's. If this is the case, you're running into the issue where QuickTime's resource file was opened earlier and then your plugin's resource was opened, putting it "on top" of QuickTime's in the resource file chain. When the resource manager is looking for a control with a particular ID, it'll see yours first and use it (unless they're specifically making theirs the "current" resource file). The solution would be for you to choose a different set of resource IDs to eliminate the conflict.
>>>
>>> steve
>>>
>>>
>>> On Jan 17, 2011, at 1:58 AM, Eberhard Ammelt wrote:
>>>
>>>> a customer has reported a problem where the popup button from a custom parameter of our plugin appears in the QT export dialog and replaces the "Include" popup button. I cannot reproduce this myself.
>>>> Does anyone know how this can happen and what I could do to avoid this? This happened with FCP 7.0.3
>
_______________________________________________
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