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
Hi! I just started using this extension and I'd like to recommend and improvement which I think could be worthwhile: If Blender is in %PATH%, do not ask for the Blender executable path and use the one from path, or offer the Blender executable found in path as another option in the VS Code prompt shown after the Blender: Start command is executed for the first time.
I'll be interested in hearing what you think about this suggestion. The ###BLENDER_TEST### check should probably be done on the %PATH% executable just in case it isn't Blender and if the %PATH% Blender fails this check, the flow would fall back to the old one.
Let me know what you think, I'll be happy to work on this if you like the idea!
The text was updated successfully, but these errors were encountered:
Thats what I was playing around in #179 before I saw the comment.
Doing the ###BLENDER_TEST### might be pretty slow though, and i am wodering about caching...
Feel ffree to comment on PR.
Hi! I just started using this extension and I'd like to recommend and improvement which I think could be worthwhile: If Blender is in %PATH%, do not ask for the Blender executable path and use the one from path, or offer the Blender executable found in path as another option in the VS Code prompt shown after the Blender: Start command is executed for the first time.
I'll be interested in hearing what you think about this suggestion. The ###BLENDER_TEST### check should probably be done on the %PATH% executable just in case it isn't Blender and if the %PATH% Blender fails this check, the flow would fall back to the old one.
Let me know what you think, I'll be happy to work on this if you like the idea!
The text was updated successfully, but these errors were encountered: