🚀 go-pugleaf

Hi, Remy,

Remy Lebeau (TeamB) <gambit47@yahoo.com> schrieb in im Newsbeitrag:
3f750c0d$2@newsgroups.borland.com...
>
> "Wim Bekker" <wim@bekker> wrote in message
> news:3f704989@newsgroups.borland.com...
>

> > But I'm wondering what exactly isn't safe. Are the VCL properties
> > at risk, or is the underlying windows structure not safe?
>
> The VCL is not thread-safe, for the most part.
Does that apply for all "Objects" of the VCL (i.e. including NON-visual
Objects and Components) or does that apply to the visual Components only
(GUI-Stuff)?

>
> > For instance, is it possible to lock the canvas of a VCL object
> > in a thread and paint on it?
>
> No.  Use Synchronize() to access the Canvas.
But I've read, especially TCanvas-Objects were "lockable" using the method
Lock() to avoid other running threads's access until Unlock() is called
after having painted to the Canvas directly.

>
> > Or is it possible to supply the windows handle to a thread to paint on
it?
>
> Possibly.
>
> > Or should this all be done in the main thread.
>
> Preferably, anything related to the GUI should be done in the main thread.
>
>
> Gambit
>
>