It really depends what you look for, and may be indeed complex (as it needs to work for all target WS).
I don't know if the LCL gtk2 uses a gtk2 label widget. Since TLabel is a GraphicControl and that means it paints directly onto the canvas of its parent. But if you take a checkbox, that would (afaik) use some gtk2 checkbox widget of the gtk2 libs.
Then you have to follow the trail through the LCL, left goes to SetBounds and so forth.
Each LCL Control has
class procedure WSRegisterClass; override;
For TCheckbox that goes to WSRegisterCustomCheckBox
function WSRegisterCustomCheckBox: Boolean; external name 'WSRegisterCustomCheckBox';
Which is like a virtual method, just without class... And at compile (actually link-) time. The linker connects this to
unit Gtk2WSFactory; // lcl/interfaces/gtk2/gtk2wsfactory.pas
...
function RegisterCustomCheckBox: Boolean; alias : 'WSRegisterCustomCheckBox';
begin
// RegisterWSComponent(TCustomCheckBox, TGtk2WSCustomCheckBox);
RegisterWSComponent(TCustomCheckBox, TGtk2WSCustomCheckBox);
Result := True;
end;
And then TGtk2WSCustomCheckBox is where everything for the checkbox connects to the gtk2 libs.
And then you have code like
TWSWinControlClass(WidgetSetClass).FooBar // class cast and method may vary
which is where the LCL call that connection.
And so, when you change Left, then it will eventually be forwarded into the gtk2 ws code, and then be given to the gtk2 libs.
Of course, for Left that is only if a control has a widget in the gtk2 libs. Otherwise its drawn internally.