TSLBasicGenericComplex.SynchronizeType
(Automated Syncronization with Documentation) |
(Automated Syncronization with Documentation) |
||
| Line 11: | Line 11: | ||
| − | stNone - does not synchronize. It will execute the callback | + | [[Enum item SLTypes.TSLSynchronizeType.stNone|stNone]] - does not synchronize. It will execute the callback |
event directly from the SignalLab thread. You should not | event directly from the SignalLab thread. You should not | ||
access any resources used by other threads or any GUI without | access any resources used by other threads or any GUI without | ||
| Line 18: | Line 18: | ||
| − | stQueue - does synchronize and queue all the buffers with the | + | [[Enum item SLTypes.TSLSynchronizeType.stQueue|stQueue]] - does synchronize and queue all the buffers with the |
main thread. It is safe to access any main thread resources | main thread. It is safe to access any main thread resources | ||
safely, including any GUI, however it will use a lot of | safely, including any GUI, however it will use a lot of | ||
| Line 27: | Line 27: | ||
| − | stSingleBuffer - queues only the latest buffer. Any other | + | [[Enum item SLTypes.TSLSynchronizeType.stSingleBuffer|stSingleBuffer]] - queues only the latest buffer. Any other |
buffer will be dropped. This is used when you want to display | buffer will be dropped. This is used when you want to display | ||
any GUI information related with the buffer, and don't want | any GUI information related with the buffer, and don't want | ||
| Line 37: | Line 37: | ||
<code> | <code> | ||
| − | SLGenericComplex1.SynchronizeType := stSingleBuffer; | + | SLGenericComplex1.SynchronizeType := [[Enum item SLTypes.TSLSynchronizeType.stSingleBuffer|stSingleBuffer]]; |
</code> | </code> | ||
| Line 43: | Line 43: | ||
<code> | <code> | ||
| − | SLGenericComplex1->SynchronizeType = stSingleBuffer; | + | SLGenericComplex1->SynchronizeType = [[Enum item SLTypes.TSLSynchronizeType.stSingleBuffer|stSingleBuffer]]; |
</code> | </code> | ||
| Line 49: | Line 49: | ||
<code> | <code> | ||
| − | SLGenericComplex1.SynchronizeType = stSingleBuffer; | + | SLGenericComplex1.SynchronizeType = [[Enum item SLTypes.TSLSynchronizeType.stSingleBuffer|stSingleBuffer]]; |
</code> | </code> | ||
Latest revision as of 00:30, 26 June 2013
This is a Beta Read Only version of this page. Please review and send recommendations to mitov@mitov.com. We will enable the editing as soon as we are happy with the overall Wiki site.
Description
Use this property to specify the type of thread buffer synchronization for the generic filters.
stNone - does not synchronize. It will execute the callback event directly from the SignalLab thread. You should not access any resources used by other threads or any GUI without critical sections or other means of protection.
stQueue - does synchronize and queue all the buffers with the main thread. It is safe to access any main thread resources safely, including any GUI, however it will use a lot of memory. Indeed once when it queue couple of hundred buffers, it will stop dropping buffers in order to prevent running out of memory.
stSingleBuffer - queues only the latest buffer. Any other buffer will be dropped. This is used when you want to display any GUI information related with the buffer, and don't want to do that for each buffer, but just for the most recent one.
Delphi example:
SLGenericComplex1.SynchronizeType := stSingleBuffer;
C++ Builder example:
SLGenericComplex1->SynchronizeType = stSingleBuffer;
Visual C++(MFC) example:
SLGenericComplex1.SynchronizeType = stSingleBuffer;
Visual C++/CLI example:
genericComplex1->SynchronizeType = Mitov::SignalLab::SynchronizeType::SingleBuffer;
C# example:
genericComplex1.SynchronizeType = Mitov.SignalLab.SynchronizeType.SingleBuffer;
VB example:
GenericComplex1.SynchronizeType = Mitov.SignalLab.SynchronizeType.SingleBuffer
