Interesting idea … where in Sublime Text would you see these commands appearing?
I apologize for breaking console output, I got focussed on preventing multiple instances of the Simulator starting with each new “build” and didn’t notice my “solution” caused console output to get lost. Fixing the issue for real is a bigger job than just Sublime Text scripting but it’s coming along nicely on both Windows and MacOSX.
In the meantime, you can return to the old behavior on MacOSX (console output but a new Simulator every time you hit Cmd+B ) by editing the file:
~/Library/Application Support/Sublime Text 2/Packages/Corona Editor/Corona SDK.sublime-build
and changing the “cmd” entry in the “osx” section to be:
"cmd": ["/Applications/CoronaSDK/Corona Simulator.app/Contents/MacOS/Corona Simulator", "$file\_path/main.lua"],
If you combine that with the Simulator’s “Reload project when files change” preference you can just use “Cmd+S” to trigger a reload of the project.
Thanks for the temp fix, Perry. Come to think of it, the old corona plugin I used with sublime also spawned new simulator windows with each Cmd+B. I got used to the Cmd+S reload so didn’t run into the multiple simulator window issue much. Glad to hear you have a better solution in the works, though.
-Stephen
Thanks, I fixed it… <3 workflow
Hmm. May have to drop using this plugin, at least temporarily:
With the old, unofficial stuff I could type things like “setRef” and get the “setReferencePoint()” autocomplete. Now I only get “sign:setReferencePoint()” unless I type out the entire “setReferencePoint”, in which case it autocompletes as is without the ().
My guess is that the plugin is unable to recognize or work with table objects, such as “myBox.outer”, whereas it probably works fine with “outer” itself. If you guys can fix this, that would be great. In the meantime it’s just too much typing.
EDIT: Yeah, none of the commands work with table objects. Yikes. Hope this can be solved. 
I’m sorry for quoting, and sorry for posting on an old thread like this but I had to get your attention somehow. I wonder if anybody is paying attention to this: http://feedback.coronalabs.com/forums/226389-corona-editor/
I have a feature request and I think it is an easy one.
Well, I’m looking forward to it
I’m sorry for quoting, and sorry for posting on an old thread like this but I had to get your attention somehow. I wonder if anybody is paying attention to this: http://feedback.coronalabs.com/forums/226389-corona-editor/
I have a feature request and I think it is an easy one.
Well, I’m looking forward to it
Is there a way to navigate through functions via click? I mean some kind of “Jump to definition” when you ctrl+click a function name in the code.
Is there such an option? or do I need to install a special package to add this feature? I’ve seen “SublimeCodeIntel” but it does not support Lua :\
Roy.
Hello, I’m also having problems with the Corona Editor plugin for Sublime Text 2, when I’m debugging the game and the code moves to a new scene, the debugger creates a new file and the simulator stops there, Am I doing something wrong? I haven’t been able to move from the main.lua file.
Is there a way to navigate through functions via click? I mean some kind of “Jump to definition” when you ctrl+click a function name in the code.
Is there such an option? or do I need to install a special package to add this feature? I’ve seen “SublimeCodeIntel” but it does not support Lua :\
Roy.
Hello, I’m also having problems with the Corona Editor plugin for Sublime Text 2, when I’m debugging the game and the code moves to a new scene, the debugger creates a new file and the simulator stops there, Am I doing something wrong? I haven’t been able to move from the main.lua file.
hey there! is it normal that i still experience the issue of multiple instances of simulator window? using sublime text 3 clean install and the latest public release of corona sdk, whenever i use cmd+b or cmd+f10, simulator opens in a new window and the old one freezes. any solution?
No, it’s supposed to stop the old Simulator when you start a new one.
What operating system are you running? Is there anything in the console (hit Ctrl+` to see the Sublime Text console)? Make sure to kill off all the “stuck” Simulators, it’s possible that one being stuck might cause them all to become so.
hey there! is it normal that i still experience the issue of multiple instances of simulator window? using sublime text 3 clean install and the latest public release of corona sdk, whenever i use cmd+b or cmd+f10, simulator opens in a new window and the old one freezes. any solution?
No, it’s supposed to stop the old Simulator when you start a new one.
What operating system are you running? Is there anything in the console (hit Ctrl+` to see the Sublime Text console)? Make sure to kill off all the “stuck” Simulators, it’s possible that one being stuck might cause them all to become so.