Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Executable path does not expand env vars if they were declared in the Variants environment #51

Open
1 task done
alainxi opened this issue Jan 16, 2025 · 0 comments
Open
1 task done

Comments

@alainxi
Copy link

alainxi commented Jan 16, 2025

Is there an existing issue for this?

  • 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 :
Image

Result :

Image

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 :

Image

Relevant log output:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant