[Lazarus] LCL-fpGUI widgetset and COM interfaces

[José Mejuto]

Hello Lazarus-List,

Monday, January 10, 2011, 3:37:21 PM, you wrote:

>> Currently the lack of regions in fpGUI (At least
>> I had not found them) is driving me crazy, but that's the "funny"
>> thing :)
GG> Not sure what that has to do with my original question, but I'll try and
GG> answer.

Nothing, just bring to my mind as I'm working on it right now :)

GG> Do you mean methods like the following:
GG>   TfpgBaseCanvas = class(
)
GG>     procedure   SetClipRect(const ARect: TfpgRect);
GG>     function    GetClipRect: TfpgRect;
GG>     procedure   AddClipRect(const ARect: TfpgRect);
GG>     procedure   ClearClipRect;
GG>   end;
GG> If not, then what is the difference between regions and clip rectangles?
GG> Where, or for what, would you use regions?

A region is more complex, it could have rectangles or any kind of
path, so for WinAPI compatibility I had created a simple workaround
for rectangles (as far as I know LCL only uses rectangles) and to
operate them because you can add cliprects but you can not read the
cliprect if it is a combination of two rects.

I'm not using regions, is LCL which use them (testing TLabel). Anyway
this is becoming off topic ;)

-- 
Best regards,
 José