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
It's a minor inconvenience that could be addressed with an addition to the docs really.
Basically the new rebranding now installs (in OSX) as Corona-<version> so you need to rename your install dir as CoronaSDK in order for the editor to work.
It would be awesome if the editor would have a preference that would allow you to launch a specific version of the SDK. I always keep many versions installed for testing but can only debug with the one that's named CoronaSDK.
The text was updated successfully, but these errors were encountered:
We'll fix the issue raised by the change in the install directory name but in the mean time you can use the corona_sdk_simulator_path preference documented here to specify the version of Corona you want to run.
It's a minor inconvenience that could be addressed with an addition to the docs really.
Basically the new rebranding now installs (in OSX) as
Corona-<version>
so you need to rename your install dir asCoronaSDK
in order for the editor to work.It would be awesome if the editor would have a preference that would allow you to launch a specific version of the SDK. I always keep many versions installed for testing but can only debug with the one that's named
CoronaSDK
.The text was updated successfully, but these errors were encountered: