On Tue, May 1, 2012 at 3:14 PM, patspiper <[email protected]> wrote:
> I think he wants to use > LCLIntf.Frame3d(DC: HDC; var ARect: TRect; const FrameWidth : integer; > const Style : TGraphicsBevelCut): Boolean > > In that case, he must add LCLIntf to his uses clause. > Yes, LCLIntf must be added to uses clause but still there is no ambiguity and thus no danger of calling a wrong function by accident. They all have different parameter signatures. I still don't quite understand the original problem. Global in ExtCtrls : procedure Frame3D(ACanvas: TCanvas; var ARect: TRect; TopColor, BottomColor: TColor; const FrameWidth: integer); Global in LCLIntf : function Frame3d(DC: HDC; var ARect: TRect; const FrameWidth : integer; const Style : TGraphicsBevelCut): Boolean; TCanvas (2 overloaded versions) : procedure TCanvas.Frame3d(var ARect: TRect; const FrameWidth : integer; const Style : TGraphicsBevelCut); procedure TCanvas.Frame3D(var ARect: TRect; TopColor, BottomColor: TColor; const FrameWidth: integer); Juha
-- _______________________________________________ Lazarus mailing list [email protected] http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
