If Titanium Studio is launched with a new workspace, and the titanium cli is installed, and the titanium sdk is installed in a non-default location, and the cli config knows about this location: studio ignores the titanium sdk path in the cli and assumes the default. This adds usability overhead because the user has to cancel the latest sdk download prompt (when studio is launched in a new workspace), then manually set the titanium sdk path to the non-default location.
This is a studio setup issue that would improve clean workspace installs for existing developers with non-default titanium sdk locations and the titanium cli.
Steps to Reproduce:
1. Move Titanium SDK to non-default location.
2. Set the location using cli command 'titanium config path.sdks <path>'
3. Run Studio with a new workspace (assuming node.js and titanium cli are installed).
User prompted to download latest sdk because the non-default sdk location is not found. User must cancel prompt and manually select titanium sdk in the studio preferences.
Studio creates workspace, asks cli for titanium sdk location, sets location and user is ready to go.