Search the Community

Showing results for tags 'qt'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Company news
    • General announcements
  • ftrack Studio (main app)
    • General discussion
    • Feature requests
    • API
    • Help
    • Actions and Widgets
    • ftrack Go
  • Connect and plugins
    • General discussion
    • Connect package releases
    • Feature requests
    • Help
    • Connect plugins releases
  • Reviews
    • General discussion
    • Feature requests
    • Help
  • Advisory Forum
  • Tech preview
    • API
    • New integrations
    • Studio overview
    • ftrack Review


There are no results to display.

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Found 3 results

  1. Hello, I've updated the ftrack python api (1.3.1) and installed the latest ftrack connect (0.6.2). I can launch an app like Maya from the browser, but my custom plugins within the app aren't finding the binding. I have in my own virtual env, but it seems to be looking for bindings from within the ftrack connect files: ... File "path\ftrack_connect\\", line 251, in <module> File "path\ftrack_connect\\", line 248, in _init ImportError: No Qt binding were found. # Any ideas how to solve this? EDIT: Also, when I try to do something like: from Qt import QtWidgets I get the same error. So it looks like the path isn't on the python path, but it's there when i check using os.getenv in maya
  2. Hey, We're looking to get some better integrations with ftrack into our own offline interfaces of our pipeline. At this moment we're working off of a great foundation in the studio with an explorer (browser), asset loader, app launcher and lots of other tools. The intentions now are to mix these up with ftrack, like pull thumbnails from ftrack and push information to ftrack upon publishes, etc. As such I'm wondering what way we should go about this. Widgets Would we be designing our own Widgets using the API completely from scratch? Or can we use widgets from connect in our own interfaces? Are the widgets in connect intended to be used that way? Things that would potentially make it easy to display thumbnails of an asset (or other information)? Connect Would the integrations require a running connect? Or when would we use it specifically? Integrating ftrack into our tools What's the best way to go about this? Any tips from the community are also very welcome! It would be great to have informational up-to-date widgets that are all built to be smoothly cached internally. Yet at this stage it's hard to see if I'm building from the ground up or if there are elements I can connect together to get up and running faster (and even share back?)
  3. Hi I have an action, that creates folders and opens them as an explorer window. This action may not always complete successfully if certain things are not set up correctly. So I want to be able to notify the user that the action has failed. There is a 5 sec time out on actions that presents them as failed if there isn't a reply. Unfortunately as the action can at times take longer than 5secs before it can be determined if it ran OK or not, so I had to reply before doing my stuff. `self.session.event_hub.publish_reply(event,data)` That's all fine, but now I need to provide a further message back to the user to say "actually its not worked and here's why". I thought seeing as it doesn't seem possible to send further replies, (presumably because the webpage stops looking after its received one), I could just show a `PySide.QtGui.QMessageBox` with my message. However it seems I can't as the environment my action is running in, already has a QApplication started, and my action is running in a thread that is not the Main GUi Thread. Are there any suggestions on how I could either use QT or in some way provide visual feedback to the user about what has happened? One thought I had which is not Ideal, but could be work able is to Popen a separate Python thread which can launch my window and receive cmd args about msg, but the msg might cover multiple lines making that not so practical. I did consider using a job but It just didn't feel quite right the action normally takes less than 5 secs. Thanks Phil