🚀 go-pugleaf

Thank You, Remy,
I hope, my following question still belongs to this newsgroup topic:

Remy Lebeau (TeamB) <gambit47.no.spam@no.spam.yahoo.com> schrieb in im
Newsbeitrag: 3f8198e0$1@newsgroups.borland.com...
>
> "Matt Heling" <heli@nospamheling.de> wrote in message
> news:3f818e8c@newsgroups.borland.com...
>
> > Does that apply for all "Objects" of the VCL (i.e. including
> > NON-visual Objects and Components)
>
> Yes, other than the thread-synchronization objects (TEvent,
> TCriticalSection, etc).
>
Is it possible (and useful) to write a BCB-VCL-Component (nonvisual during
runtime) using two or more threads, nevertheless?
Because:
I'm trying to write a component, which in one thread fetches data from some
hardware (measurement data), whenever data should be ready to be fetched,
stores the data immediately into memory buffer (a kind of a Fifo) and
"tells" the other thread, it would now be allowed to read the data, when it
would be ready to do so. By doing so, I'm hoping to make the component able
to fetch each occuring dataset on one hand, and to have enough time to
process the data on the other hand (independent from the "fetch thread").
"Process the data" should mean in that case: The component shall work as a
dataprovider for subsequent (using) dataprocess-components.

(I'm afraid, this question actually belongs to the
...vcl.components.writing-group, but this is almost the only group
discussing threads...You have my apologies. ...)

Thanks

Heli