I really appreciate the new console on Mac, by the way. It’s the little things, you know. 
I would have to agree with that. I’ve been using an automator script written several years ago that launches Corona Terminal in a way that I could have a Corona icon in my doc and get a terminal. Now I don’t need that any more.
Rob
That’s funny. I’ve just been clicking the bland Terminal icon.
I for one don’t like it. 
I’m using Sublime Text (with Corona Editor) and it already has a nice console log at the bottom of the window when an app is started. So the new Console Log window that pops up is redundant (and annoying since a new window is opened every time the app is run).
On a Mac, if anyone wants to get rid of it it’s an “easy” fix. Just type on the command line:
defaults write com.coronalabs.Corona_Simulator no-console -bool true
If you want it back you can just change true to false above.
@CoronaLabs. (FusePowered??)
This should really be a setting under Corona Simulator’s Preferences instead of having to hack the defaults-registry manually.
Could someone shed some light on why I now get this error message when I start the simulator on Mac (OSX 10.10) ?
“console.sh” can’t be opened because CoreServicesUIAgent is not allowed to open documents in Terminal.
I did see the new console log window open up once a couple days ago, but since then I get that error popup message instead. I’d actually like to have it available (and agree it should be a toggle in the Simulator Prefs)
The only time I’ve seen that is if I tried to double-click the old “Corona Terminal” item which was mistakenly in a couple of Daily Builds.
Does this happen if you double-click “Corona Simulator”? Does it happen with the current Daily Build?
Thanks Perry. I updated to daily 2505 (from 2502) and that fixed the problem.
In daily build 2506, the “Corona Terminal” has been completely removed. Is this a permanent change?
I prefer to start the Corona Terminal from the command line. I been using this for years, why would you take this away?
Yes, this is a permanent change. It more matches the Windows behavior where launching Corona SDK with it’s Icon starts Corona SDK AND it starts the terminal for you. You can disable this if you want (instructions above), but the idea here is that you can drag the Corona SDK app to your dock and just launch it from there. You get a Corona Icon instead of a Terminal Icon using the other method.
If you want to start it from the command line do:
open /Applications/CoronaSDK/Corona\ Simulator.app/
Rob
If you open the Corona Simulator from the command line, is there a way to tell it what project to load and start running?
I tried to cd to the directory that contains a valid corona project, and then run the following command:
open /Applications/CoronaSDK/Corona\ Simulator.app/ $PWD
But that didn’t work.
open -a /Applications/CoronaSDK/Corona\ Simulator.app/ .
(the . and $PWD should do the same thing, . means current directory) Also this works too:
open -a /Applications/CoronaSDK/Corona\ Simulator.app/ ~/Projects/CoronaSDK/Business\ Sample\ App/
Rob
I’m using Textmate with the Ludicrous bundle for Corona…
Cmd “R” used to launch my project and with the new daily build, this is broken. I tried setting SDK_PATH to “/Applications/CoronaSDK/Corona\ Simulator.app”
but that’s still throwing some obscure error from the TM Bundle engine…
I’m not thinking clearly right now…can anyone tell me what I need to change in my Textmate config to work with this new change to the terminal setup??
Thx
Dewey
What did you have before? What errors are you getting?
Rob
Hey Rob…thanks for the reply.
Before this problem, I did not have an SDK_PATH variable set on Textmate2…
I added it based on this link but that link is about TM v1 and I’m running V2
And actually I am a little mystified as to how the Cmd “R” in the bundle was finding the Corona Terminal previously…I still don’t know but obviously I need to find a way to tell it how to find Corona\ Simulator.app
The error seem useless to me its:
Failure running “Run Simulator”.
793:794: syntax error: Expected “"” but found unknown token. (-2741)
OK, I figured it out…to fix Textmate for the new launch context:
Edit the Cmd “R” part of the Corona Bundle to look like this:
if [[${#SDK_PATH} > 0]] ; then
CORONA_SIM_PATH=$SDK_PATH
else
CORONA_SIM_PATH="/Applications/CoronaSDK/Corona Simulator.app/Contents/MacOS/Corona Simulator"
fi
I second that, thanks for the tip, really annoying that terminal opening up without asking for it.
And i agree, it should just be an option in the preference, not a mandatory “we decided it will be like that now”.
Just to add, I just note that each time you open Corona, a new console is open. But when you quit Corona, the console keeps there on screen. So, if you are like me (that likes to close the simulator while you make changes in the code), you soon get stuck with a dozen of terminals on screen.
The console opens when I open simulator.app, but I’m not getting any readout to the console for errors or print() outs. This applies for a new project I’ve just started and all previous projects. Previous builds with the Corona Terminal worked great.
What’s happening with this build? I’m forced to use build 2484 (last build with Corona Terminal) in the meantime.
Thanks in Advance,
Ash
Yup, this is broken. I use it with Glider and get the error, you also seem to get it with Sublime, probably other editors too.
This really needs a disable option in the settings.
For now I might use that terminal provided above.