On Tue, 04 Dec 2007 15:38:10 +0300
Andrey Gusev <[EMAIL PROTECTED]> wrote:
> Anyway, at now, codetools still unusable!
>
> I already collect all my sources to project, also collect all my
> support sources to packages (by Mattias Gaertner hints).
> I also prescript all conceivable paths to all path boxes.
> Nevertheless, when i press Ctrl+Shift+SpaceBar, i got "Error: unit
> not found".
>
> Enought labour was spended to that problem (common with Mattias
> Gaertner).
> I need feature to see codetools searching process details with normal
> IDE functionality mode
> (--debug-log do not give enough information about codetools units
> searching process).
>
> I ready to be participated in development such feature/tool, but i
> need more technical
> information about codetools searching process.
It starts in function TFindDeclarationTool.FindUnitSource and calls
DirectoryCache.FindUnitSourceInCompletePath.
If you do not use the 'in' modifier then a normal search takes place.
TCTDirectoryCache.FindUnitSourceInCompletePath fetches the
CompleteSrcPath from the CodetoolBoss, which is the value you can see
in IDE's unitinfo.
Then it searches the unit with
TCTDirectoryCache.FindUnitSourceInCleanSearchPath.
You can try adding some debugln, to see where it goes wrong.
> I cannot give all my (production) sources, but, in case, root project
> and packages sources be attached.
> Also --debug-log output included (if it not useless... WorkrXtr
> cannot be found).
Mattias
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
