saying there is no println() or that println() is not implemented is factually incorrect.I don't think I ever said that or at least I never meant to say that. I keep on emphasizing that it is lcd.println() that is not supported. Take another look at reply #17.
I think we finally agree.
I think we may have mostly always agreed.
I believe that you probably always meant "not supported" but you kept typing
"there is no" or "not implemented" even in responses #17 and #19.
The words "not supported" is never mentioned in any of your posts (other than #22)
but I kept using those words over and over again.
So it kept jumping out at me.
It is the specific language that was (and still a little bit) bothering me.
There were some factual inaccuracies in references to "implemented", "supported", "exist",
that were bothering me.
In post #1:
S-2) Tried to use lcd.println. There is no such function so you will see two strange characters with your text
To which my original response in # 14 was:
S-2 is already there, but I'd change the language from:
"There is no such function" which is incorrect to
"It is not supported by most of the lcd libraries including the LiquidCrystal library that ships with the IDE".
but then in #17
I still maintain that there is no lcd.println() function.
But there is a lcd.println() function. While there is no println() in the current LiquidCrystal API documentation
on the Arduino web site, which implies that it isnt' supported, it still does exist.
Currently if a person does call it, it does not work as would be expected.
And then in #19:
It may be true that println() can be made to work as expected with other LCD libraries but the fact remains that at the present time it is not implemented in the LiquidCrystal library. Therefore it's use in a sketch that incorporates the LiquidCrystal library is incorrect.[/color]
This is where things get a bit tricky since technically neither print() nor println() are implemented
in LiquidCrystal since they are both implemented in Print.
But it is "implemented" since Print is inherited by LiquidCrystal.
I assume you really meant "not supported" rather than "implemented".
Things seemed to have gone south after my response in #14, not sure why.
It seemed quite simple to modify the language of "There is no such function" to "It is not supported".
Maybe it was latter part of that #14 post that referenced scrolling. I mentioned that because it
came up in another thread, where the user was using println() and was expecting that
the output would wrap and would scroll up and ended up getting 2 funky characters instead.
In #21 What I was trying to say was the print() and println() *always* do exist and are implemented
but they are both implemented in Print which LiquidCrystal uses so both will exist in LiquidCrystal
and that since the current LiquidCrystal code shipping with the IDE does not handle newlines,
not only is println() not supported but any use of newlines embedded in strings sent to print() will
not work either.
So it is beyond println() not working with LiquidCrystal, it is any use of newlines
that won't work with the LiquidCrystal that currently ships with the IDE.
This includes both println() and newlines embedded in strings sent to print().