David HAROUCHE wrote:

>>> Better use a private TBitmap to the thread, and give public access 
>>> to a built-shadow TBitmap of it via a property of the Thread....

>> are not thread safe unless you lock them.

> This sounds obvious when working with concurrent processes !

What I meant is that TBitmaps that are declared private to a thread aren't so
private, because they register themselves in a global list which is accessed by
the garbage collector in the mean thread.


Normally locking is only required if an object can be accessed by multiple
threads. For TBitmaps you always need locking if you work with them in a
thread. Even if you declared them as private or local in a thread method.


Jan Derk