I have an error compiling in v1.0. It explains the error in the bottom window in brown text, but there is no line number. It does not move the cursor to the error like it did before in 0022? Why not? How can I find the line number easily? I have tried many different types of errors that I made up to test it. It does not highlight the error. Tried no ;. Tried misspelling keywords.
0022 highlights the entire line in bright yellow. Nice! Should I stick with 0022?
I started 1.0 (on Win7 64 bit), opened the blink without delay example, scrolled down, and changed OUTPUT to OUT_PUT in the pinMode() call. I clicked the Verify button. The line with the error was highlighted in yellow, and the line number with the error was shown in the lower part of the window.
If the IDE can not figure out which line caused the error, it can't highlight it.
So, you need to post some specific code.
Alright I've completely lost my mind... The hallucinations are getting worse...
Fortunately I have a witness, 2 different PC's, it's a mass hallucination!
then post your code if it still doesn't work, we won't be able to help you otherwise...
sbright33:
I have tried many different types of errors that I made up to test it. It does not highlight the error. Tried no ;. Tried misspelling keywords.
1.0's error highlighting is working for me in the case of bad syntax. I see it quite often. 
Sorry I can't reproduce the error. Yesterday I tried 3 different types of errors, all of them failed to turn yellow.
Will ask my friend to try it, he had the same problem, with different code.
What kinds of errors have no line to highlight? I realize it may be incorrect, but 0022 always guesses.