Beta 7 adds builds for Xcode simulator, a device information API, improved texture memory management, a Show Project Sandbox menu item in the simulator, and a number of important bug fixes.
Really nice stuff. What I am missing more right now is the ability to have asynchronous http requests (an xml parser would be nice too :)
I second that d3mac123, asynchronous requests would be really really great. I've found that they are required in most situations, and the use for synchronous requests is fairly limited.
GOOD WORK!
Hum... my Game crashes on the iPhone Simulator but not on the Device... I'll send tom an email with my current project code.
I've got an app that crashes only on beta 7... (working on beta 5, beta 6)
@Sunny ... I am sure that the changes in Memory Management will break some apps... I told this to tom and I think that they have to few informations on what have changed!
Is it really a crash? Or does it "bail out?" ... Are you remove()ing and re-insert()ing display objects probably?
Thanks Ansca for these fantastic features, but my game (built with Corona Beta 7, it doesn't have physics) doesn't work in the iPhone simulator.
Is it possible that since I'm using Xcode with iOS 4, the build doesn't work for compatibility reasons?
Please continue discussion of Xcode simulator in this forum thread: http://developer.anscamobile.com/forum/8
@Sunny, please make sure to read the release notes in http://developer.anscamobile.com/downloads/beta under "Improvements to memory management". If this is not your issue, please mail support at anscamobile dot com with details, or post details in the Beta forum thread http://developer.anscamobile.com/forums/beta. Thanks!
Me too,
I got many trouble with my application
With the simulator all ok but
It crashes in the xcode simulator and in the Ipad it opens but don't receive touch events in 90 % of cases
With Beta 6 all works correctly in simulator and ipad
Same for me. App works in the simulator but not on xcode. i will check the other thread as suggested.
Fixed. See other thread.
@ OderWat & @Eric : Thanks for your help.
I think that the main crash problems came form remove() (group:remove( indexOrChild )).
I've modified a few lines in my code and now it works perfectly ! thanks for your help
Please see my thread http://developer.anscamobile.com/forum/2010/07/13/my-experince-trying-port-corona-iphone-app-android
Beta 7 does NOT address the major problems with Android: A) The application can't recover from being suspended and then restored (the screen is either blank or corrupt), B) Sound events don't work. playEventSound() doesn't work (I have tried with .mp3, .wav and .ogg files), media.playSound() works fine (including with MP3) but media.stopSound() doesn't.
Any comments from the developers???
Gary
Gary, I'm sorry but I don't develop for Android since I don't have an Android device.
Our Android developer was on vacation during part of the Beta 7 release cycle, and that release focused on other priorities.
For event sounds on Android, you have to preload them with newEventSound() and play them after a delay with playEventSound(). What delay? We can't say. The Android API (SoundPool, if you are interested) doesn't signal when load is completed, until Froyo. Yes, this needs to be documented better, I'll open a case about that. #556.
I'll test stopSound (again) today.
Eric,
Thanks for your reply... and thanks for that golden nugget of information... I now have sound for playEventSound() working perfectly with .ogg files (I haven't tried any other formats, since .ogg is working)...
What I do now is pre-load ALL of my sound events at the start of the application and then just call them when necessary... Works great!
Now if I had only known that like 3 weeks ago... But never mind...
I will update my thread...
Thanks,
Gary
PS. No luck getting a viable workaround for the suspend problem... More in my thread: http://developer.anscamobile.com/forum/2010/07/13/my-experince-trying-port-corona-iphone-app-android
This is really good stuff! The Device Info is a huge relief. It does pretty much everything I would have wanted, the only thing I would really like to see in the future is the ability to get the actual device screen size, no matter what the content scaling mode is set to.