How to avoid autoscroll in CVI?

[Andrey_Dmitriev]

Colleagues,

Very simple but stupid question:

I using Intel C++ compiler together with CVI. Every time when I have errors/messages/remarks, then the opened file scrolled automatically to the first line. I guess its happened, because Build output looks like that:

This output shown above caused "autoscroll" to the line 1, instead of line 60.

The question is - how to suppress "Intel banner", or how to disable "autoscroll" feature?

Thank you advance,

Andrey.

[PeterAdelhardt]

Hi Andrey,

I do not have the Intel compiler installed but here is what I would try: In The Compiler Settings (Build Options) you can adjust your configuration. Here, you could try to set the warning level to "default warnings" instead of "all warnings". In the "advanced" menu you will be able to choose even more settings. In "compatibility flags" you could also enter your own command line flags.

The flags that can be used in order to display and suppress warning messages and the like can be found in the Intel compiler documentation. 

The settings window:

Hope this helps!

Regards

Peter

[Andrey_Dmitriev]

Hi, Peter,

Thank you for reply, but it doesn't work.

When all warnings are disabled (already tried this), then the output still have first three lines, and window scrolled to the first line.

I tried /nologo switch, but it doesn't work as well.

Its a problem with output parcer in CVI or with transferring /nologo switch to icl command line.

with best regards,

Andrey.

[Andrey_Dmitriev · Accepted solution]

Ah, I have found my trouble now.

These lines coming from iclvars.bat, not from icl .exe. /nologo switch works.

So, I have removed according echo lines from iclvars.bat (first two lines) and vsvars32.bat (third line), and now output started from the line where an error or warning occurred.

Now source code window auto scrolled properly.

One small cosmetic bug report for NI: if I perform double-click in the build output window on the error/warning line, then source window scrolled properly, but cursors stops blinking and stay invisible (until arrows button pressed).

Andrey.

Message Edited by Andrey Dmitriev on 03-30-2010 03:27 PM

[PeterAdelhardt]

Andrey,

thanks for clarifying what caused the issue. I am glad you found out how to avoid these additional output lines!

Regards