If you’ve seen the Daily Build release notes lately, you’ll notice that more and more Android features and fixes have been coming through at an alarming rate! Today I’m going to highlight some of the more prominent features and fixes that have been recently pushed-in, but I highly encourage you to go check out the latest Daily Build and see for yourself.
There’s a lot of great stuff, so I’m really just scratching the surface here, but here are the highlights nonetheless:
As of Daily Build 2011.653, we now have Android + Sub-directory support with all Corona-specific functions! This means you can place images and audio in sub-directories and access them with the corresponding Corona functions (display.newImage(), audio library, etc).
NOTE: You’ll still have trouble with some Lua functions + sub-directories though, so “io” calls to files in sub-directories (which include images and HTML) still aren’t supported.
Assets Not Getting Updated
There was a pretty nasty Android issue that affected developers who released updates to their app, where the update would intend to replace existing asset files (text, images, audio, etc.) wouldn’t get replaced. Instead, updates only installed newly added files, and updates to the Lua scripts. Previously, the only workaround for this was for the user to uninstall the app and re-install the app. Obviously a pretty nasty bug.
Now, users can update their app, and everything you intended to get updated will! If you replaced an image or audio file in your update, those files will also be updated when the user goes to update the app on their device. Needless to say, if you are an Android Corona developer, you definitely need this fix! (casenum: 8830)
Hide Video Controls
Previously, when you called media.playVideo() on Android, the video controls (e.g. the play button, pause, etc) would stay on screen. We now support the ability to hide the video controls on Android.
Oldie But Goodie….
And last but not least… I touched on this briefly in a previous Daily Build update, but it’s worth mentioning again.
Previously, Android builds only supported 16-bit color. This was mildly noticeable with images (although very noticeable to the graphic designers out there!), but really showed its ugly face when you went to apply gradients to vector objects. Now, as of Daily Build 2011.643, we now support 32-bit color on Android!
Here’s a before-and-after shot that our Android/Windows engineer, Joshua Quick, was dying for me to show you guys: