@Brent, you’re my hero.
Which is exactly why a number of us wrote about this same topic when display.newText() was made to use setFillColor() to change the color of text. Just can’t understand why a SDK would not aim to be consistent.
display.newText’s are rendered graphics in the display library. You are technically setting the fill color of the graphic. All display.* uses setFillColor. The native.* context is more Text, not filling a graphic so setTextColor() makes more sense.
Rob
Ah makes sense of course if you look at it that way… Problem is…
We are all here because we chose to program in a “High-level programming language” which in general is expected to abstract the details of how a program actually runs on the computer and offer the programmer a natural language (as in… English) interface to those pesky 1s and 0s…
In other words, we shouldn’t have to remember how a word is drawn on the screen and then say therefore I will color this one with setFillColor() while I will color that other one with setTextColor()… It just doesn’t make sense to have two different ways to color text. Please pick one or the other and abstract the intricacies.
Your honor, I rest my case! :)
I believe this is related :
2013.2113
Mac/iOS: setTextColor now works correctly for 0-1.0 rgb ranges casenum:28862