First, thank you Corona-team for an awesome update !
I just updated Corona SDK from 2014.2511 to 2015.2646.
I have a small annoyance, when using print(), Corona outputs the message, then adds another newline (consecutive debug messages have an empty line between them).
Is there a method to print the debug without adding the newline? (note that in the previous public build, this didn’t happen)
I know it’s something small and stupid, I’m just wondering if I can revert this.
Can you be more specific. It this occurring in the simulator and on the device. In either case, which:
Windows Corona Simulator Y/N
OS X Corona Simulator Y/N
iOS Device Y/N
Android Y/N
I ask, because on the iOS device, the print output is a little goofy an as I recall gets an extra newline. I don’t think this is something the Corona Team can change. (We had a talk about this earlier last month…can’t find post right now.)
Engineering will want a bug report on this. Must make a simple main.lua with your two print statements in it, include a config.lua and build.settings and put it in a zip file… Make sure to include information like that it’s the Windows simulator only. Copy/Paste your log output. Include the link to this forum post.
When you get the email with the bug report case #, please post it back here.
Can you be more specific. It this occurring in the simulator and on the device. In either case, which:
Windows Corona Simulator Y/N
OS X Corona Simulator Y/N
iOS Device Y/N
Android Y/N
I ask, because on the iOS device, the print output is a little goofy an as I recall gets an extra newline. I don’t think this is something the Corona Team can change. (We had a talk about this earlier last month…can’t find post right now.)
Engineering will want a bug report on this. Must make a simple main.lua with your two print statements in it, include a config.lua and build.settings and put it in a zip file… Make sure to include information like that it’s the Windows simulator only. Copy/Paste your log output. Include the link to this forum post.
When you get the email with the bug report case #, please post it back here.