in the latest build, Corona is now printing stuff like this for every print:
2012-10-01 10:28:25.467 Corona Simulator[73290:f03]
is there a way to turn that off? It makes the logs very hard to read since Corona is also wordwrapping at some low number in the console.
[import]uid: 122310 topic_id: 31539 reply_id: 331539[/import]
No there isn`t.
Its is the hard-work of CoronaLabss Team that already got it printing out for us using the resources of [lua]NSLog[/lua] of the system, because without that we could still be without the print statements due to Apple`s changes regarding iOS6.
So, its isnt fault of Corona, opposite of it btw.
PS: Better to see these prints than nothing at all.
Rodrigo. [import]uid: 89165 topic_id: 31539 reply_id: 125992[/import]
@Rodrigo, thanks for your feedback on my concern. Although it says I’m a Test Driver in the forums, i’m actually a paid Enterprise customer, so I think its perfectly fine to make suggestions about how to improve the product for paid users.
I’m not aware of a reason that Corona Simulator would need to use NSLog instead of the printf method. …I think NSLog is just for devices or XCode builds. At least a setting to allow us to switch between them would be super helpful when doing debugging.
[import]uid: 122310 topic_id: 31539 reply_id: 125999[/import]
No problem.
Also there is not about you being test driver, pro or something else as it means nothing for me as I believe that any version of Corona should work the same way for the major part of the things and for any subscriber (of course am not saying about “features” of Enterprise version).
The issue I told you was exactly what I`ve heard about it as well and so I shared with you BUT am not saying that am 100% right and so if some Corona Staff can come in and give you a much more detailed answer, great!
Rodrigo.
EDIT: FYI: See a chunk of Corona`s blog post below:
""" As a consequence of this iOS 6 change, we also had to change the way we display errors and messages in the Mac Simulator. We now use NSLog to display our messages which results in adding a date/time stamp in front of all the messages. This, and other changes we may be forced to make to fix the iOS 6 print issue, may also affect how the information is displayed in the Mac Simulator console. This could affect third-party Corona programs that rely on our console and error messages (using stdout and stderr).
One of the side benefits of this change is the Mac Console app will now receive Corona runtime (and soon print) data from both the Corona Simulator and iOS Simulator. The eliminates the need to open a Terminal window to view Corona Simulator and Build messages. “”"
source: http://www.coronalabs.com/blog/2012/09/19/faq-wednesday-iphone-5-and-ios-6/ [import]uid: 89165 topic_id: 31539 reply_id: 126001[/import]
ah, good find! OK, seems like NSLog is here to stay. I’ll just find a way to trim out that stuff when displaying in my text editor. [import]uid: 122310 topic_id: 31539 reply_id: 126005[/import]
No there isn`t.
Its is the hard-work of CoronaLabss Team that already got it printing out for us using the resources of [lua]NSLog[/lua] of the system, because without that we could still be without the print statements due to Apple`s changes regarding iOS6.
So, its isnt fault of Corona, opposite of it btw.
PS: Better to see these prints than nothing at all.
Rodrigo. [import]uid: 89165 topic_id: 31539 reply_id: 125992[/import]
@Rodrigo, thanks for your feedback on my concern. Although it says I’m a Test Driver in the forums, i’m actually a paid Enterprise customer, so I think its perfectly fine to make suggestions about how to improve the product for paid users.
I’m not aware of a reason that Corona Simulator would need to use NSLog instead of the printf method. …I think NSLog is just for devices or XCode builds. At least a setting to allow us to switch between them would be super helpful when doing debugging.
[import]uid: 122310 topic_id: 31539 reply_id: 125999[/import]
No problem.
Also there is not about you being test driver, pro or something else as it means nothing for me as I believe that any version of Corona should work the same way for the major part of the things and for any subscriber (of course am not saying about “features” of Enterprise version).
The issue I told you was exactly what I`ve heard about it as well and so I shared with you BUT am not saying that am 100% right and so if some Corona Staff can come in and give you a much more detailed answer, great!
Rodrigo.
EDIT: FYI: See a chunk of Corona`s blog post below:
""" As a consequence of this iOS 6 change, we also had to change the way we display errors and messages in the Mac Simulator. We now use NSLog to display our messages which results in adding a date/time stamp in front of all the messages. This, and other changes we may be forced to make to fix the iOS 6 print issue, may also affect how the information is displayed in the Mac Simulator console. This could affect third-party Corona programs that rely on our console and error messages (using stdout and stderr).
One of the side benefits of this change is the Mac Console app will now receive Corona runtime (and soon print) data from both the Corona Simulator and iOS Simulator. The eliminates the need to open a Terminal window to view Corona Simulator and Build messages. “”"
source: http://www.coronalabs.com/blog/2012/09/19/faq-wednesday-iphone-5-and-ios-6/ [import]uid: 89165 topic_id: 31539 reply_id: 126001[/import]
ah, good find! OK, seems like NSLog is here to stay. I’ll just find a way to trim out that stuff when displaying in my text editor. [import]uid: 122310 topic_id: 31539 reply_id: 126005[/import]