Author Topic: Tracing compiling errors in the source  (Read 3309 times)

Offline Micky

  • Single posting newcomer
  • *
  • Posts: 8
Tracing compiling errors in the source
« on: January 18, 2011, 09:26:36 am »
It's good to be here, welcome to everybody, and - here's my first question: After experimenting quite a lot with different environments, I decided to switch to C::B, but right from the beginning - in my view - I'm missing an important feature: with Dev-C++ or Netbeans ide's I simply used to left-click on a compiler-error-message and the cursor automatically jumped to the said source code position! In C::B I just get a (red) line with a corresponding line number, which I have to trace manually.

What I'm doing wrong?

Thanks for your kind help!

Offline killerbot

  • Administrator
  • Lives here!
  • *****
  • Posts: 5514
Re: Tracing compiling errors in the source
« Reply #1 on: January 18, 2011, 09:34:47 am »
note there are 2 tabs with compiler output :
1) Build log : this is simple text output
2) Build messages : this is a synopsis list of warnings and errors, and when you double click those entries you are taken to the offending line in the source code.
« Last Edit: January 18, 2011, 10:29:45 am by killerbot »

Offline Micky

  • Single posting newcomer
  • *
  • Posts: 8
Re: Tracing compiling errors in the source
« Reply #2 on: January 18, 2011, 10:26:02 am »
Ooohhhh ... I'm sorry, I should have noticed that :oops: Thanks a lot for your fast help!

P.S.: single-click capability is not available?
« Last Edit: January 18, 2011, 10:29:24 am by Micky »