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