Hi Bob,
I changed this by typing int and tested it again earlier as I mentioned above and the same thing happened when I did it.
Cheers,
John
If it was incorrect the compiler would have thrown an error.
Hi John
Not what I meant. I said to delete the line containing that term and type it manually again using “uint16_t” as before. Replacing with “int” I think just gets you back to the “255” situation you were trying to rectify.
Anyway you seem to have a work around which works for you so all good.
Cheers Bob
Hi Jeff.
Not necessarily. Sometimes something quite invisible happens during the copy and paste procedure. It has happened to me 3 times now I think. The first time I copied a whole sketch to try a couple of things and do you think I could get it to work. I compared my version with the original just about character by character and I could not see any difference. The sketch compiled OK and I thought that would fail if there was an error. In desperation I typed the whole thing manually (it was not very big) and the damned sketch worked as expected.
I believe this has happened to others and I don’t think anyone has really got to the bottom of it yet. I have not heard anything anyway. Could maybe be an invisible non printable character in there somewhere making things look like a comment (similar to “//”) and ignored so the compiler does not see an error. I don’t know. Brain is too fuzzy these days to worry too much. As long as I can fix it.
Cheers Bob
