On Thu, 15 Nov 2007 22:56:22 +0300 Andrey Gusev <[EMAIL PROTECTED]> wrote:
> * Mattias Gaertner <[EMAIL PROTECTED]> [Thu, 15 Nov 2007 > 19:16:55 +0100]: > > > > If a directory is not in the unit search path, then it will not > get > > > > the project settings. > > > > > > AG: From which (search) paths, have a few tunables ? > > Sorry, my english is not good enough. What do you mean? > > The "Other sources (used only by IDE)..." tunable - that setting, > what "will not get" ? The compiler. > > > AG: That is all fine, but the full control ability (of search > > > process) interested to me ! > > > > What do you mean with interested in full control ability? > > Do you want to know all places/flags that control the final unit > > search path? Or do you want one more possibility to control/setup > > the unit search path? > > I must precisely knows how tune project settings to all my units be > found (i already knew it, thanks to ours disscussions). > That sense: if whatever fundamental don't works properly, then > secondary things is unimportant. > apropos: "--debug-out" is usable to penetrate into units searching > process ? --debug-out is mainly for windows, where the normal hints to stdout are hidden. With --debug-out=log.txt you can save the IDE hints to a file. Normally the IDE only writes some basic hints. The IDE can be compiled with various flags to get a lot more output, but this only usable to hunt bugs and hardly used, so this is not documented. See for example the header of components/codetools/finddeclarationtool.pas for a list of possible verbosity flags. Normal users (including developers not used to these parts of the IDE) should use the Source Editor / Popup Menu / Unit Info. > (about bad IDE behaviour) > > An example how to improve it. > I have a few (the two) ideas, but at first i must explore sources and > do some experiments with it. > > > The IDE now skips silently missing units when searching for > > ancestor > forms. > I have redirect dialog messages (the first simple idea) form > dialogprocs.LoadCodeBuffer() to my own logger window. > Thanks for your respond. It will be reflect to bugtracker ? Please give feedback in the bug tracker, what part of the bug is still open. > The second idea - about event reactors insertion, but she is not > complete. Mattias _______________________________________________ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel