I really wish more work could be done to properly update the documentation when new features are added. I believe we are all wasting lots of time trying to find information on new features that are not clearly documented, if documented at all! Not everyone has the time to read whats in the new builds and god knows where else all over the corona website. Perhaps i’m not aware of the page everyone finds out the new features and how they all work but even though im using .652 i only just read abt the retina and embossed text abilities. There’s nothing mentioned at all abt these in the documentation of display.newText. Please guys get someone to properly update the documents for all of our sakes, it’s already a headache enough developing games without the need to search high and low (and in most cases through google!) how some of the corona features work! [import]uid: 66228 topic_id: 17452 reply_id: 317452[/import]
+1 [import]uid: 44010 topic_id: 17452 reply_id: 66201[/import]
+1 [import]uid: 64502 topic_id: 17452 reply_id: 66207[/import]
- 1 [import]uid: 30314 topic_id: 17452 reply_id: 66210[/import]
Good points, I will get on it [import]uid: 84637 topic_id: 17452 reply_id: 66311[/import]
Thank you Danny,
You have idea how it is important for whom is learning right now! 
[import]uid: 89165 topic_id: 17452 reply_id: 66314[/import]
Ideally, it would be nice if the documentation could be versioned similar to how the Django documentation is.
This way, you always get the most recent version of the docs, but non-subscribers, or developers targeting older builds, can still get accurate documentation. New features are documented for those on the cutting edge, and those same new features are hidden for legacy developers, reducing confusion as to why a particular feature isn’t working in older code. [import]uid: 52771 topic_id: 17452 reply_id: 71211[/import]
+1 [import]uid: 15571 topic_id: 17452 reply_id: 80515[/import]