Getting Rid of Incorrect Red Squiggly Lines in D2005 and D2006

[John Jacobson]

I've noticed that there are quite a few entries in QC about Error Insight
incorrectly flagging symbols with the red squiggly line even though the code
compiles fine. I was seeing this behaviour in D2005 after I updated to that
version of Delphi, then I fixed it without later remembering what I had done.
Once again after I updated to D2006 I saw Error Insight incorrectly flagging
identifiers as undeclared or unknown even though the code always compiled
cleanly. This time when I fixed it I remembered what I did. Here is how to
remove a good deal of the incorrectly attributed red squiggly lines:

1) Find the directory(ies) that contain the DCU files for the incorrectly
flagged symbols.2) Add this/these directory(ies) to the Browsing Path list
found at Tools|Options|Environment Options|Delphi Options|Library - Win32.

It seems that Error Insight is using the browsing path directories, even though
the compiler pays them no heed. The result can be quite disconcerting when the
browsing directories don't point to the files containing the symbols in your
projects.

--

***Free Your Mind***

[Ingvar Anderberg]

"John Jacobson" <jake@j[nospam]snewsreader.com> skrev i meddelandet news:43a5ea56$1...@newsgroups.borland.com...

> This time when I fixed it I remembered what I did. Here is how to
> remove a good deal of the incorrectly attributed red squiggly lines:
>

Good to know, thanks !
/ia

[Reinier Sterkenburg]

This problem has bothered me and others in our team too.
I've tried John's solution as described under 1) and 2) and it
worked at first but later the problem came back.
I've now found that it helps a lot (in fact, so far this works
perfectly) if the path that contains the DCUs is placed AT THE TOP of
the Browsing Path list. Apparently there is an issue with a maximum
number of paths that can be entered(?)

Reinier Sterkenburg

[Captain Jake]

"Reinier Sterkenburg" <reinier.s...@xsFOURall.nl> wrote in message
news:4411...@newsgroups.borland.com...

> I've now found that it helps a lot (in fact, so far this works perfectly)
> if the path that contains the DCUs is placed AT THE TOP of the Browsing
> Path list.

I've noticed this too, but forgot to mention it.

[Dave Keighan]

Sorry about responding to such an old post -and- quoing everything in it but I wnt to keep hings in context for the question I have.

Reinier/Jake/All,

How far wrong am I going if I decide to have all the components I install store their DCU files in a common folder?
\Tools\_DCU for example.
I'm already telling them to use \Tools\BPL for the libraries.

This will allow/require me to add only one path the the BrowsePath and avoid the squigglies altogether.

Just a thought ...
--
Dave Keighan
XanaNewser [ 1.17.6.6]