If you do a double-click on a warning in the compiler
message window, nothing happens. It used to open the
file at the line where the warning happened.
I couldn't reproduce the problem, double clicking on a warning
goes to the correct line here. Maybe you would have a
sample project to provide that we can try to reproduce the
problem ?
Thank you,
Colin
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It seems to associate the warning with wrong line numbers,
because (in another project) it has "1" in the "Line"
column, but the real warning is in another line:
Logged In: YES
user_id=25510
I couldn't reproduce the problem, double clicking on a warning
goes to the correct line here. Maybe you would have a
sample project to provide that we can try to reproduce the
problem ?
Thank you,
Colin
Logged In: YES
user_id=591019
I will keep in it in mind and send you a sample the next
time I run into it.
Logged In: YES
user_id=609236
I'm closing this one for now - if you find an example
project where it occurs - please reopen this bug report and
attach the project
Logged In: YES
user_id=591019
Just put this into your code:
// #define TEST \ // printf("test");
It will give you the following warning (with -Wall):
1 C:\Dev-Cpp\Projects\test-dev\main.cpp:1
[Warning] multi-line comment
And if you double-click on it, it won't go there.
Logged In: YES
user_id=591019
It seems to associate the warning with wrong line numbers,
because (in another project) it has "1" in the "Line"
column, but the real warning is in another line:
1 P:\project\dev\source\base\base\exbase.h:61
[Warning] multi-line comment