Component path shows up red
1 1

27 posts in this topic

Sans Connect, are you calling session.event_hub.wait() anywhere? (either after you make the session, or inside the register function of the resolver, but I don't recommend the latter.) That's required to actually poll the event queue and respond.

I assume "Custom resolver.py NOT picked up" means that the path is still red. You can check whether the plugin has been loaded by searching sys.modules for your filename, but do note that the namespace will be a UUID.

Share this post


Link to post
Share on other sites

It works now.

I think part of the reason this thread becomes so lengthy is I didn't realize I need to have an event handler running by myself to supersede connect, so I kept asking how ftrack python api gets called.

Thanks Steve and of cause Lorenzo!

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
1 1