Erik

Members
  • Content Count

    40
  • Joined

  • Last visited

  • Days Won

    7

Erik last won the day on August 24

Erik had the most liked content!

About Erik

  • Rank
    Member

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

705 profile views
  1. Regexp for project and any created entities would be great. We got listeners for fixing most things but it would give better feedback to the people that inputted weird things instead of magically changing the name on them.
  2. Not without writing your own action to do it afaik. We requested this feature a while back as well.
  3. https://help.ftrack.com/administering-ftrack/workflows/managing-list-categories You can create Deliveries Old. That's what we do if the lists becomes to many. https://www.ftrack.com/en/2018/05/hiding-closed-lists.html You can also hide closed lists. This info don't seem to be anywhere on help.ftrack.com tho.
  4. This is one of the most sought after features here as well.
  5. Agree. I find the old docs much clearer and easier to navigate.
  6. Markdown support or support for picking foreground/background colors per row in Enumerators would be really handy. Is this something planned?
  7. I think you can speed this up greatly by collecting all the selected id's first and then querying for "id in ()" to get a collection instead of "id is " -- Erik
  8. Digging up this old thread as I am trying to check the same thing but can't find any way of seeing "last login" -- Erik
  9. Would be nice if there existed an event for this but guess we'll add it ourself.
  10. I'm digging up this old thread as well. We are making a new asset library and wanna tag versions with things like maya,maya_2017,vray,vray_3.5,character,fur,projectname and then be able to do a reasonably fast query against this through the API. Would modifying a custom enum attribute and add more values as we go along still be the best or only option? Feels like that attribute would get pretty crazy pretty quickly.
  11. Erik

    Incoming links

    Chiming in on linking Asset to TypedContext (Sequence/Shot/Task/etc). Would be really useful.
  12. We use it as a indicator of where in the tree structure you are at the moment like. '.'.join([foo.get('name') for foo in bar.get('link')]) gives for example Project.sequence.shot.task With the old api we do it in a recursive function using getParent and the end result is project.sequence.shot.task This is for a project where the Project name is Project and the Project code is project
  13. When getting the link attribute of for example a task it contains the full name of the project. I think in most cases it would make more sense to include the name aka project code instead. And if replacing it is not an option please include both. Like this we have to do an additional query just to get the project code.
  14. Adding to the define how many decimals club. Biggest problem at the moment being for example FPS. It can be 23.976 in a lot of places and I guess I could put it as text but then I have to do unit conversions everywhere which is not very elegant.