[Resolved] Lua Control code for a Space? (AKA: How do I get SublimeText2 to work with 915+?)

[richard9]

So…I knew Corona Labs had to make some serious changes to get terminal output with iOS6 and the new XCode, but I wasn’t aware that this also broke SublimeText2 and its JSON build system.

{ "cmd": ["/Applications/CoronaSDK/simulator", "main.lua"], "working\_dir": "${project\_path:${folder}}", }

That’s the basic OSX build system file that has worked for Corona SDK 600 series-800 series. Now, it says it can’t find the file. I know the .app is ‘Corona Simulator’, but renaming it doesn’t work, and if I edit the file to look for the original name, it says “can’t find Corona” - it’s cutting the second word in the filename.

So my pleas for help:

1. Does anybody have a working build setting for SublimeText2 using Corona 915 or above?
2. Does anybody know the Lua control code for a space (eg: nbsp; or whatnot). Been staring at the official Lua docs for awhile and just can’t seem to pin that one down. [import]uid: 41884 topic_id: 31839 reply_id: 331839[/import]

[nick_sherman]

Don’t know if this is any help, but to get Corona to work with IndeED I have to create a folder called simulator in the CoronaSDK and copy the .app into there. For whatever reason they decided to drop the separate folder and in this IDE the location of the .app is hard-coded. [import]uid: 93133 topic_id: 31839 reply_id: 127083[/import]

[Omnigeek_Media]

I didn’t know that Sublime could do that. I have my corona set to auto relaunch when it sees changes in the project so as soon as I save a file in sublime then I get a free reload.

This way I have a terminal screen with my console log going and the corona simulator up all the time. What does this buy you.
To answer your question try putting a \ in front of the space: Corona\ Simulator
[import]uid: 19626 topic_id: 31839 reply_id: 127108[/import]

[ivke2006]

I have the same problem and both suggestions aren’t working for me.

Anyone other suggestions?

[import]uid: 106768 topic_id: 31839 reply_id: 127119[/import]

[ivke2006]

if it helps, this is the error message in the terminal.
[Errno 2] No such file or directory
[cmd: [u’/Applications/CoronaSDK/simulator’, u’/Applications/CoronaSDK/SampleCode/test’]]
[dir: /Applications/CoronaSDK/SampleCode/test]
[path: /usr/bin:/bin:/usr/sbin:/sbin]
[Finished] [import]uid: 106768 topic_id: 31839 reply_id: 127136[/import]

[richard9]

Got it working!
EDIT: Filed a bug. (#18043)

Basically, in the .600 to .800 series, Corona included an alias file called simulator in their installer. In the current version, they have left this out. I have no idea what the alias contains (it’s not editable in a text editor), but if you can copy the file over to your new Daily Build ST2 support is back. (It’s with that really nasty timestamping as a result of Xcode, but it’s back.)

Annoying but relatively fast solution:

1. Reinstall .883
2. Copy the “simulator” alias file from the CoronaSDK/ folder to your desktop.
3. Reinstall your favorite latest Daily Build
4. Copy the alias file into the CoronaSDK/ folder.

EDIT: Note that until Corona Labs fixes this, every time you install a new Daily Build you will have to copy-in the simulator file again. The Daily Build installers will delete this file from the directory every time (regardless of the overwrite message you get on install.)

Why you want ST2 to handle Corona SDK

1. It pipes the console through a toggleable window within ST2, which means it’s easier to see what’s going on and you don’t have to manage 3 windows. If you develop on a Macbook Air like I do, this is *essential*.
2. You can use a hotkey to launch the SDK + console window and focus moves automatically to your app. Again, huge; goes straight to what you need.
3. I can think of a lot of times in Corona development where keeping the SDK open just isn’t a good idea.
   a) When building loops or other tricky functions that have a high chance of causing the SDK to hard-crash or spam the console until it crashes
   b) When you are running off battery and need to conserve power (very common on a laptop)
   c) When you need to conserve performance for whatever reason (ie: I don’t want to be running the SDK in the background when I’m doing a few other things at once)
   [import]uid: 41884 topic_id: 31839 reply_id: 127215[/import]

[nick_sherman]

Don’t know if this is any help, but to get Corona to work with IndeED I have to create a folder called simulator in the CoronaSDK and copy the .app into there. For whatever reason they decided to drop the separate folder and in this IDE the location of the .app is hard-coded. [import]uid: 93133 topic_id: 31839 reply_id: 127083[/import]

[Omnigeek_Media]

I didn’t know that Sublime could do that. I have my corona set to auto relaunch when it sees changes in the project so as soon as I save a file in sublime then I get a free reload.

This way I have a terminal screen with my console log going and the corona simulator up all the time. What does this buy you.
To answer your question try putting a \ in front of the space: Corona\ Simulator
[import]uid: 19626 topic_id: 31839 reply_id: 127108[/import]

[ivke2006]

I have the same problem and both suggestions aren’t working for me.

Anyone other suggestions?

[import]uid: 106768 topic_id: 31839 reply_id: 127119[/import]

[ivke2006]

if it helps, this is the error message in the terminal.
[Errno 2] No such file or directory
[cmd: [u’/Applications/CoronaSDK/simulator’, u’/Applications/CoronaSDK/SampleCode/test’]]
[dir: /Applications/CoronaSDK/SampleCode/test]
[path: /usr/bin:/bin:/usr/sbin:/sbin]
[Finished] [import]uid: 106768 topic_id: 31839 reply_id: 127136[/import]

[richard9]

Got it working!
EDIT: Filed a bug. (#18043)

Basically, in the .600 to .800 series, Corona included an alias file called simulator in their installer. In the current version, they have left this out. I have no idea what the alias contains (it’s not editable in a text editor), but if you can copy the file over to your new Daily Build ST2 support is back. (It’s with that really nasty timestamping as a result of Xcode, but it’s back.)

Annoying but relatively fast solution:

1. Reinstall .883
2. Copy the “simulator” alias file from the CoronaSDK/ folder to your desktop.
3. Reinstall your favorite latest Daily Build
4. Copy the alias file into the CoronaSDK/ folder.

EDIT: Note that until Corona Labs fixes this, every time you install a new Daily Build you will have to copy-in the simulator file again. The Daily Build installers will delete this file from the directory every time (regardless of the overwrite message you get on install.)

Why you want ST2 to handle Corona SDK

1. It pipes the console through a toggleable window within ST2, which means it’s easier to see what’s going on and you don’t have to manage 3 windows. If you develop on a Macbook Air like I do, this is *essential*.
2. You can use a hotkey to launch the SDK + console window and focus moves automatically to your app. Again, huge; goes straight to what you need.
3. I can think of a lot of times in Corona development where keeping the SDK open just isn’t a good idea.
   a) When building loops or other tricky functions that have a high chance of causing the SDK to hard-crash or spam the console until it crashes
   b) When you are running off battery and need to conserve power (very common on a laptop)
   c) When you need to conserve performance for whatever reason (ie: I don’t want to be running the SDK in the background when I’m doing a few other things at once)
   [import]uid: 41884 topic_id: 31839 reply_id: 127215[/import]

[ivke2006]

@ richard9:

It works!
Thank you very much!!!

[import]uid: 106768 topic_id: 31839 reply_id: 127698[/import]

[ivke2006]

@ richard9:

It works!
Thank you very much!!!

[import]uid: 106768 topic_id: 31839 reply_id: 127698[/import]