| Ganga, In the first case, you're probably getting a -parameterChanged: call on a thread other than the main thread in FCPX. If that's the case, you'll need to run your alert panel on the main thread, perhaps using [-NSObject performSelector:onMainThread:].
The timingAPI issue is a known bug that should be fixed in a future release.
By the way, I saw your other questions. I'll try to get an answer for you this week. I've been on vacation for the last 3 weeks, so sorry for the slow response.
Darrin On Jan 3, 2012, at 6:05 AM, ganga wrote:
Hi all,
I'm working on FxPlug filter for FCPX. I noticed that, FCPX
hangs most of the times if I call NSRunAlertPanel from
parameterChanged method (some times it worked perfectly). Same
code works in Motion 5 all the time. Does anyone know about this
issue?
I also noticed that timingAPI returns fps of motion template
instead of current FCPX project. I am using
timelineFpsNumeratorForEffect and
timelineFpsDenominatorForEffect APIs. Is there any other way to
get fps associated with FCPX project?
Regards
Gangaraju
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
|