Just installed the autocomplete and build package for atom using this guide. But I get an error ‘C:\Program’ is not recognized as an internal or external command,
operable program or batch file.
And for the autocomplete it doesn’t work with the build.settings file.
I’ve gotten past the C:\Program is not a recognized command, but there is another error I’ve not solved yet. You can try this path, but there is an extra “Files” being added to the project folder path that shouldn’t be.
“cmd”: “/Program^ Files^ ^(x86^)/Corona^ Labs/Corona^ SDK/Corona^ Simulator.exe”,
All that said, Corona SDK actually works better when you don’t use an editor’s build command. I know many people are used to working that way, because that’s how IDE’s typically work. But each time you run the build command you have to launch the simulator. Corona’s Simulator is designed to watch for file changes and automatically reload itself. Simply run the simulator, load your project through it’s file system interface (likely to be the #1 entry on the welcome screen that starts up and in the Recent projects list). Then edit your files in Atom and as soon as you save the file in Atom, the simulator should automatically reload the project saving you from having to hit CTRL-ALT-B.
Rob
Thanks Rob.
Does the autocomplete-corona package work with build.settings file? It doesn’t highlight the text for me.
Autocomplete does not work for the build settings last I checked
I don’t use Atom, but in Sublime the editor that I do use, it does syntax highlighting based on file extension. .settings are not .lua files. I don’t know if the syntax highlighter can be written to also look at .settings files. I’ll ask the folks who made it and see what’s possible.
Rob
In Sublime you can change the syntax highlighting on a filetype by filetype setting for the session by clicking at the bottom where it says “Plain Text”. But this change isn’t permanent.
Atom has a similar “Plain Text” at the bottom that you can click on and change to Lua for syntax highlighting. I don’t believe this will save it as permanent either.
Rob
I’ve gotten past the C:\Program is not a recognized command, but there is another error I’ve not solved yet. You can try this path, but there is an extra “Files” being added to the project folder path that shouldn’t be.
“cmd”: “/Program^ Files^ ^(x86^)/Corona^ Labs/Corona^ SDK/Corona^ Simulator.exe”,
All that said, Corona SDK actually works better when you don’t use an editor’s build command. I know many people are used to working that way, because that’s how IDE’s typically work. But each time you run the build command you have to launch the simulator. Corona’s Simulator is designed to watch for file changes and automatically reload itself. Simply run the simulator, load your project through it’s file system interface (likely to be the #1 entry on the welcome screen that starts up and in the Recent projects list). Then edit your files in Atom and as soon as you save the file in Atom, the simulator should automatically reload the project saving you from having to hit CTRL-ALT-B.
Rob
Thanks Rob.
Does the autocomplete-corona package work with build.settings file? It doesn’t highlight the text for me.
Autocomplete does not work for the build settings last I checked
I don’t use Atom, but in Sublime the editor that I do use, it does syntax highlighting based on file extension. .settings are not .lua files. I don’t know if the syntax highlighter can be written to also look at .settings files. I’ll ask the folks who made it and see what’s possible.
Rob
In Sublime you can change the syntax highlighting on a filetype by filetype setting for the session by clicking at the bottom where it says “Plain Text”. But this change isn’t permanent.
Atom has a similar “Plain Text” at the bottom that you can click on and change to Lua for syntax highlighting. I don’t believe this will save it as permanent either.
Rob