🚀 go-pugleaf

"Lapo" <lapoguidi@inwind.it> wrote in message
news:3ed163fb@newsgroups.borland.com...

> But, first of all, it's really better to use messages
> instead of using Synchronize method?

As was previously mentioned, up to and including BCB5, Synchronize() is
implemented to use messages via SendMessage().

The other way in general to do what you ask is to just protect the actual
data with a synchronization object such as a critical section, mutex,
semaphore.  Then you don't have to deal with all this message/Synchronize()
stuff.  Since you can't really protect access to a VCL component using any
of these if the component resides in the main VCL thread (unless the
component itself uses them internally), it would be better to protect access
to the JPG data itself.  Then the retreiving thread can safely update the
data whenever it has new data available, and the VCL thread can safely grab
the currently available data periodically whenever it wants and pass it to
the display component.  Only 1 thread will be able to gain access to the
data any any given time and any other thread that wants access will have to
wait until the other thread already accessing the data has finished its
tasks.


Gambit