Workfile not offered at start if no workfile exists

[jakubjezek001]

Is there an existing issue for this?

• I have searched the existing issues and added correct labels.

Please describe the feature you have in mind and explain what the current shortcomings are?

Currently the workfile tool gui is opened first, before Harmony session is created. This is causing issue since it is offered even no workfile version is available yet. Usually user need to close the workfile tool before Harmony can be fully opened. It is annoying and makes no sense.

Suggested implementation?

Harmony integration should check first if there is any workfile version available and if not, then not to offer workfile tool at start up.

Describe alternatives you've considered:

No response

[BigRoy]

Out of curiosity - what's the reason we're starting the workfiles tool first anyway (and especially have this enabled by default)?

Anyway, to remove this behavior, remove the AYON_HARMONY_WORKFILES_ON_LAUNCH env var from Application Environment in ayon-applications settings ayon+settings://applications/applications/harmony/environment

I'd even argue that - if possible - we should remove the feature and instead support the core feature ayon+settings://core/tools/Workfiles/open_workfile_tool_on_startup to launch workfile tool on startup. For which the actual implementation logic I believe currently only exists in Nuke and Houdini

---

Ah, I've only learned now that Photoshop, After Effects and Premiere have this same implementation currently using an environment variable.

Likely there's some reasoning behind this due to them being "external python process" hosts. (Even though recent versions of Harmony do have Python API support)

[AnhTuWally]

@jakubjezek001 @BigRoy This PR should address the issue.

#55