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

FYI: The new Corona rebranding breaks this plugin #23

Closed
poisa opened this issue Jul 1, 2017 · 2 comments
Closed

FYI: The new Corona rebranding breaks this plugin #23

poisa opened this issue Jul 1, 2017 · 2 comments

Comments

@poisa
Copy link

poisa commented Jul 1, 2017

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.

@ghost
Copy link

ghost commented Aug 25, 2017

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.

@ghost
Copy link

ghost commented Sep 26, 2017

This is fixed in release 1.7.0

@ghost ghost closed this as completed Sep 26, 2017
This issue was closed.
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