The release notes specify:
Android: Added “object.alpha” property support for native fields such as TextField, TextBox, and WebView. An alpha value of 255 is opaque and 0 is transparent.
Why does this depart from using values between 0 and 1 to indicate transparency? This should be standardized. [import]uid: 105599 topic_id: 29229 reply_id: 329229[/import]
I suspect its because those are native objects and not openGL objects and the rules are different. [import]uid: 19626 topic_id: 29229 reply_id: 117521[/import]
That was a documentation mistake on my part. I just fixed the release notes now. On Android, the alpha property works exactly like how it does on iOS. 1.0 is opaque and 0.0 is transparent. Trust me, it works exactly like that.
Yeah, that was one of those head slapping moments for me. Our release notes are automatically generated based on our commit messages from our repository. Unfortunately, there is no “undo” to what you commit to a repository… which is by design. So, I have to wait until the daily build gets published and then edit the release notes page. D’oh. [import]uid: 32256 topic_id: 29229 reply_id: 117600[/import]
Perfect! Thanks for the clarification Joshua! [import]uid: 105599 topic_id: 29229 reply_id: 117613[/import]
As an added bonus, I’ve made the alpha property work with WebViews on Android too. You can display a semi-transparent WebView with an alpha property of, say, 0.5. That’s something that is currently not supported on iOS (at least via Corona; I don’t know if it’s an iOS limitation), which only supports fully opaque or fully transparent alpha values. [import]uid: 32256 topic_id: 29229 reply_id: 117622[/import]