General ⇒ Finding where Error occurs in TeXniC Center

[manic21]

Hello

I'm fairly new to TeXniC but I've searched hard all over google but can't find an solution to this problem, so in desperation I've come here! I'm writing my PhD Thesis in LaTeX using TeXniC Center and I have each Chapter in a different tex file and I'm using the "project tool" to help organise my thesis. Everything seems fine, it compiles, it gives error messages which can be corrected.

BUT! I've noticed that what I click on an Error ( Red circle with cross inside) in the Output Bar, I'm not automatically taken to the file\line where the error occurs. The same goes for when I try to use the "Next Error (F9) Button on the Tool bar (which only takes me to the error label in the output bar, but doesn't jump to the error in the source file).

This behaviour doesn't happen with single file LaTeX code.

Is it a bug in TeXniC Center, or a shortcoming? Has anyone else noticed this? Has it always been like this or is it just because I'm using version 1 Beta 7.01, which may be particularly buggy? Could you please help me find a way around this bug/feature.

Thank you for reading, Best Regards

N

PS: I'm using the latest version of MikTeX (2.6.2646) and TeXniC center (1 Beta 7.01)

[ishermandom]

I am having this problem with the latest version (1 Beta 7.01) of TeXnicCenter as well, even with single-file documents. Specifically, when there is an error, I would expect double clicking the error in the console window at the bottom to take me to the location of the error in the source code. This worked just fine in previous versions, but doesn't seem to work in the latest version. Also, it is worth mentioning that this only happens in the pdfLaTeX mode; when producing DVI's, everything works as expected.

Any help would be greatly appreciated!

[whugemann]

I have the same problem with newer versions of the TeXniCCenter. On my computer, this error does not seem to be linked solely to pdfLaTeX, but affects more or less all output modes. (Thus the solution is not that easy as switching to another output mode.)

I have just noticed that there is a similar (unanswered) topic at
http://www.latex-community.org/viewtopi ... Jump#p4873

Greetings from Münster, Germany
Wolfgang Hugemann

[Saippuakauppias]

Yes, the bug rests. But where to report it?

[rebo2]

I am having the same problem in 1.0 Stable. My searches show a number of people have had this problem but I don't see a fix that I can use. Please post if you know how to fix this.