Hi, I moved this Lazarus related thread here from FPC-devel list.
> Mattias Gärtner wrote: >>> What gave no feedback? >> >> Ok, I tested again with a non-typical situation. >> I worked with lazarus.lpi and built Lazarus from tools -> Configure Build >> Lazarus. The error messages show up just like when compiling a "normal" >> project but "search identifier" does nothing. > > I tested with lazarus.lpi: It works. > Do you have english messages? Yes, the problem was elsewhere. The tool tries to find the source file in project directory, "lazarus/ide" in this case, but the problematic file was in "lazarus/converter" directory. When I created a similar problem in a file in ide directory, it worked as expected. >> Now I tested with a "normal" project and it works. It is a cool feature >> actually. >> I noticed a minor bug: the Scope combobox gets "Project" by default. If I >> click the down-arrow to see a list then the first "Lazarus IDE" gets selected >> automatically. I guess you forgot to set Combobox.ItemIndex and only set its >> text. > > It didn't matter for me. I now set the ItemIndex. Does that fix it? There seems to be again a difference between GTK2 and QT bindings behavior for combobox. I don't know which one is more correct though. QT version seems to select the item pointed by ItemIndex, GTK2 version does not. Now it is worse than before because you set a wrong ItemIndex (I guess, didn't look at code). "Project" is the second item so ItemIndex should be 1 but it is apparently 0 instead and "Lazarus IDE" gets selected without touching anything. That is for QT version. GTK2 version also shows "Lazarus IDE" hilighted when opening the list but doesn't select it unless you press enter. >> BTW, what does the Scope do? If I comment out SysUtils in my source, >> it always finds the missing function under FCL, whatever scope I >> select. > > That's the interesting difference between the codebrowser and a find > declaration. Find declaration will search only via the uses sections > and search paths. The codebrowser searches in whole packages and > projects. That's why it can tell you in which unit an identifier is > defined. > If you set scope to 'project' it will search in all units of the > project. If you check the 'with packages' it will search in all > packages required by the project too. This normally includes the FCL > package, so it will search in all units installed by FPC. Right, thanks, now I understood the logic. 'with packages' is selected by default (which is good) and it always found FCL functions. Regards, Juha
-- _______________________________________________ Lazarus mailing list [email protected] http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
