Separate Dependency Options for Macros

[NeoInfiniTech]

When a macro that is not "installed" is inserted to a workflow (from a folder), its dependency can also be modified (including the macro inputs, if there are any) from the Workflow Dependencies settings.

I would like to suggest that the macro tools and the relevant files have separate buttons for dependency configurations.

One use case for this would be when a user saves a workflow in a specific location after configuring the paths as All Relative and moving the workflow to an entirely different folder afterwards, making it difficult to find the original location of the macro used in the workflow, also introducing the chance of breaking the workflow when opened and saved with the undefined (question mark sign) macro tool if the underlying workflow XML is not examined by a text editor.