I'm using the Current and fully updated version of Atmel Studio. I have noticed, if an error is generated while compiling, The line numbers given by the error message is always 7 lines higher than the actual line number where the problem exist. At first it was kind of confusing because I did not find the error where it was supposed to be. Now that I realize the problem I can quickly find the error. But it is still kind of annoying.

Is it just me, or has anyone else come across this problem.

Thank you.

Joe.

Atmel Studio 6.1 2730 service pack2.

I opened a basic sketch "blinking".

I manufactured in error at the end of the sketch by adding a "}".

Compiled the sketch and got this error message.
" 
Compiling 'Blink' for 'Arduino Due (Programming Port)'
Blink.ino:29: error: expected declaration before '}' token
Error compiling
"
since the sketch ends at line 25, I know that there's something wrong.

And no I have not altered the "Validation Skip" property. Where would I find it.


Thank you for your help.

Joe.

"if might actually be a bug if the very last line is reported to Visual Micro/Arduino as an error. Errors in all other lines will probably work okay?"Off

No, The problem persists no matter where the bug is in the code. It can be on the first line, on the last, or anywhere in between. It does not matter. I only use that example because it was very obvious something was wrong.
However I have noticed that the Error does change. Sometimes it is 5 lines off, and sometimes it is more. 

I appreciate any help you can give.

Thank you.

Joe.

Since I was always in the general area where the error would occur, I never tried it. I normally do one modification at a time. I went back to the "Blink" sketch and tried it. Although it is hard to tell on such a small sketch, it did tend to take me to the general area. But not the exact location. Although some errors are kind of ambiguous, and hard for the program to pinpoint exactly, specific errors such as missing semicolons, invalid variable names, and misspelled keywords, should be easy to spot for the program. In these cases the program did take me to the exact line number.

Also, while investigating this problem I noticed something else. When I closed the program it asked me if I wanted to save the changes. I clicked no. I did not want to save the error. Yet the changes were saved to the "Blink.ino" anyway. When I reopened the file the error was still there. I had to make sure all the errors were clear and the sketch was running properly before I close the program. Normally when I close the program I want to save all changes, so this issue has not come up before.

I appreciate your assistance.

Joe.

I simulated that error, on a sketch that I'm working on.
Actual line number was "555".
Reported line number was "566".
When I double-click the error message it correctly took me to line number "555".

I also created a similar error in the "blink" sketch, with similar results.

The discrepancy seems to be in line numbers only. 

As far as the autosave function goes, no libraries were added.
I only had the file open for a short time, just enough to create an error and verify what was happening. When I exited the program, I click no I did not want to save the changes. But it saved it anyway. It is one thing to save the changes to a temporary file and then transfer it to the original file. But it should not alter the original file without your permission.

I appreciate your assistance.

Joe.

"ps: Did you try the xFeatures extension in Atmel Studio, color codes errors/warnings. Very nice "

Thanks for the information. I will take a look at that.

As far as the Autosave feature before the  build, that makes sense. But can I make a suggestion. In the future Versions, have it save the file to a Temporary File, instead of the main file. That way if something should go terribly wrong, you don't lose your previous work. 

Thank you for your help, And I hope this helps the program.
This platform is much better than the original Arduino IDE.
Sometimes it's the little bugs "mosquitoes" That annoys us the most.

Joe.