Yes, good point, also rename display/noDisplay for on/off as in lcdapi,. that Print.h I will think, because that is something very hard to implement by logic on segment char display. They are very specific, if you use those with symbols or pre-writen labels. Of course for those, which are just 6 digits 7seg or 14seg that setCursor and print will work just fine, because I can claim them as single row 6 column char lcd.
but in LCDAPI is mandatory for example blinking cursor, that is something, what those segment LCD does not supports at all.. but if I will use LCD API only as "starting reference point" and not as "must be it like that", then I can just omit that.
for now I will try somehow to replace writeChar and writeFloat with print for that segment parts.
But do not know if you look for that library as-is now, because I have there writeChar, which use LCD Section (like top, clock, temp,...) in order where to print. If I will use setCursor, how it will confuse users about what is row 0, row 1 if for example one segment has 1st row 4 digits with : in middle for clock, space, 1 digit for day of week
2nd row 4 digits for temperature 1
3rd row 4 digits for temperature 2
also what will happen if someone will set cursor to 0, 0 and will write 10 chars? Asking because now I have section CLOCK and I will not allow to print there more than 4 chars (or I will show just first 4), because in RAM/Memory map of this LCD if I will continue writing in memory, it will overflow to symbols like T1: symbol or % symbol or clock symbol on this T1T2 LCD for example.
maybe I can do something like
setCursor 0,0
print 1234
setCursor 0,5 (or 0,1?)
print 5
setCursor 1,0
print 23.4
setCursor 2,0
print 51.2
Really have to think about compatibility with Print.h class and meaning of those very specific Segment displays
