You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched the existing issues and added correct labels.
Description
Current Behavior
In Applications addon settings, for example in the Blender settings for an executable path, environment variables do not work if the env vars were declared in the "Variants" environment.
Expected Behavior
It would be very useful to support these env vars, as it allows to have different env var depending on the DCC version : 4.0, 4.2, etc...)
Steps To Reproduce:
In the Applications addon settings, for example if the env var is declared in the "Variants" environment of Blender :
Result :
Additional context:
But the same env var declared in the "Variants" environment, is correctly expanded when it is used in the main Blender env var field (above/outside the Variants part).
So, this works all right :
Relevant log output:
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Description
Current Behavior
In Applications addon settings, for example in the Blender settings for an executable path, environment variables do not work if the env vars were declared in the "Variants" environment.
Expected Behavior
It would be very useful to support these env vars, as it allows to have different env var depending on the DCC version : 4.0, 4.2, etc...)
Steps To Reproduce:
In the Applications addon settings, for example if the env var is declared in the "Variants" environment of Blender :
Result :
Additional context:
But the same env var declared in the "Variants" environment, is correctly expanded when it is used in the main Blender env var field (above/outside the Variants part).
So, this works all right :
Relevant log output:
The text was updated successfully, but these errors were encountered: