-
Notifications
You must be signed in to change notification settings - Fork 44
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
Adding a runtime selection dropdown into the editor #35
Conversation
This sort of works but we don't seem to have enough rights to update the registry key. Looking into that. |
e6b382a
to
f77208a
Compare
Ok, so I couldn't get changing the registry entry through our plugin to work because of rights issues. But with a pretty dirty hack I was able to get it to work with |
f77208a
to
307d4e4
Compare
307d4e4
to
a7ce6b8
Compare
a7ce6b8
to
aec9a11
Compare
@ChristophHaag I've completely changed this to be based on the environment variable. |
aec9a11
to
11ba50b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
With the home directory fix it works nicely on linux.
Short wishlist (maybe for the future):
- Show the full path somewhere in the ui (tooltip on the dropdownbox?)
- Persistently store the selected runtime
- Allow adding runtimes from the UI
I've added the tooltip but the other two I think we should do in new PRs. |
11ba50b
to
18fde6a
Compare
@ChristophHaag if you can have another quick look, I think this is ready to be merged. It works really well imho |
looks good to me |
Adding a dropdown (windows only) to the editor that allows us to select from different (known) runtimes:
![image](https://user-images.githubusercontent.com/1945449/108299445-8dcd5300-71f2-11eb-8059-fd51f7075c57.png)
The known runtimes are stored in
runtimes.json
in our addons folder so we can easily add more entries. On reading the JSON we will check if the paths to the runtime files exist and only offer those we find. We'll probably need to make it smarter to check the same path on different drives in case the user has decided to install Oculus/Steam on a D: or E: drive or something but that is for an enhancement PR.If the current runtime is not found in the list, it is added (in editor only, the
runtimes.json
is not altered).