I’m not wrong because I said I don’t know of any game developers who think of colors in that way. It could be that I just don’t know the game developers you know. But my point was, and I’d bet money it’s right, that most devs don’t *think* of colors in that way. As in, come up with colors 0-1 in their heads.
And that has nothing to do with the solution that would have allowed 98% of Corona devs to continue using 0-255 while the ones who care about a larger color palette can do that, too:
setFillColor(0-255, …)
setFillColorHD(0-1, …)
Adding features is good. Breaking existing code is bad. I think CL could have gone to Gfx2 without breaking things – you can deprecate things over time and do an end-of-life later.
Example: object:setReferencePoint(display.CenterLeftReferencePoint) could have done an anchorX=0 and anchorY=.5 under the hood along with a warning that setRefPt was deprecated and to stop using it – but it would still work. That would have allowed maintenance and updates to go on for a while without things breaking.
Yes, it requires more back-end coding and yes, the resulting code is not as optimized as it could be, but that would only be a problem for the people who continue using the deprecated API calls.
Jay