I have just looked at the documentation out of interest to ‘see what I need to change’ in my app.
Well my first comment is ‘wow’ heeavvy… plus there is an obvious lack of diagrams of these new concepts and how they fit with the older hierarchy of ‘objects’.
[Greg have you tried graphicsCompatibility = 1]
It would help to start at the Stage level and provide step by step diagrams (plus code) of the hiearchy of all these concepts so that frames, levels, Anchor points, groups and children and so on can be visualised more easily by the Corona user/app developer.
There is far too much reading and re-reading required to understand if there is a bug or a miss-understanding. Further when simple tests fail it does not give users confidence that they understand anything…
But I am pleased to see, at last, that there is some ‘backward compatibility’ at last being considered instead of pure deprecation.
[in Graphics 2.0, reference points have been deprecated. Anchor points must be used in their place unless you decide to use V1 Compatibility Mode]
_ . _
Back when ‘I was a lad’ deprecation was never spoken of [in fact it was a swear word] and everything had backward compatibility because of maintaining customer confidence and reducing the amount of re-work costs for the users. Nothing was shipped without backward compatibility testing and simple test cases validation ‘sign off’ before a build was released.
I will try my apps with the {graphicsCompatibility = 1} this week as there are so many critical placements that took me weeks to get right and I dont look forward re-working all that code and thought processes…
