Quote from: howardpc on November 17, 2016, 11:55:28 amIt looks as if for some reason the .lpr of your project omits the Interfaces unit.Lazarus 1.6.0 gives the same warning in that situation. I don't know how the update can affect it.Maybe there are mixed .ppu and .o files from the old revision. Just rebuild Lazarus and its packages clean. Usually it solves all problems.
It looks as if for some reason the .lpr of your project omits the Interfaces unit.
sudo apt-get install gdb
@tr_escapeInstall debugger on Debian/mint/ubuntu:Code: [Select]sudo apt-get install gdbIf gdb is installed, but you get the same message for some reason, try adding it manually:first, find out where is gdb installed:Code: [Select]whereis gdbYou should get something like this:Code: [Select]gdb: /usr/bin/gdband add it manually (or browse to it).
I would like it very much if Lazarus and the controls finally started to recognize it when you have your Windows taskbar in another location then at the bottom.IIRC. the previous version at least recognized it when you maximized the main Lazarus window, but now it pops behind the taskbar.It also tends to restore the windows at the wrong location.
gdk_monitor_get_workarea ()voidgdk_monitor_get_workarea (GdkMonitor *monitor, GdkRectangle *workarea);Retrieves the size and position of the “work area” on a monitor within the display coordinate space. The returned geometry is in ”application pixels”, not in ”device pixels” (see gdk_monitor_get_scale_factor()).The work area should be considered when positioning menus and similar popups, to avoid placing them below panels, docks or other desktop components.Note that not all backends may have a concept of workarea. This function will return the monitor geometry if a workarea is not available, or does not apply.Parametersmonitora GdkMonitor workareaa GdkRectangle to be filled with the monitor workarea.
SystemParametersInfo function with the SPI_GETWORKAREA value.
@dogriz,Thank you so much gdb issue is solved.But I had to remove lazarus 1.6.2 and I reinstalled the 1.6.0 for now.I'll try later.
I think there is a issue inside of UTF8SearchInStringList function.
line 1648Code: Pascal [Select] // project uses lcl unit Forms if (UTF8SearchInStringList(MainUsesSection,'interfaces')>=0) or (UTF8SearchInStringList(ImplementationUsesSection,'interfaces')>=0) then and I changed to this lines:line 1648Code: Pascal [Select] // project uses lcl unit Forms if (UTF8SearchInStringList(MainUsesSection,'Interfaces')>=0) or (UTF8SearchInStringList(ImplementationUsesSection,'Interfaces')>=0) then
function UTF8SearchInStringList(List: TStrings; const s: string): integer;begin if List=nil then exit(-1); Result:=List.Count-1; while (Result>=0) and (UTF8CompareText(List[Result],s)<>0) do dec(Result);end;
Can you undo the changes above an try this?If you go to the ($Lazarus)/ide/ideprocs unit, line 1286Code: [Select]function UTF8SearchInStringList(List: TStrings; const s: string): integer;begin if List=nil then exit(-1); Result:=List.Count-1; while (Result>=0) and (UTF8CompareText(List[Result],s)<>0) do dec(Result);end; and change UTF8CompareText to CompareText, does it also fix your problem?(All unitnames are in ASCII, so there currently is no need to use Utf8 functions in that code).If this also solves your problem, this indicates that there is an issue with Utf8CompareText or WideCompareText.Also, if this fixes it, what is your locale?Bart