TSLBasicGenericComplex.SynchronizeType - Revision history

David Alm: Automated Syncronization with Documentation

2013-06-26T00:30:11Z

Automated Syncronization with Documentation

← Older revision		Revision as of 00:30, 26 June 2013
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>

David Alm: Automated Syncronization with Documentation

2013-06-26T00:29:54Z

Automated Syncronization with Documentation

← Older revision		Revision as of 00:29, 26 June 2013
Line 11:		Line 11:


−	~~[[Enum item SLTypes.TSLSynchronizeType.~~stNone~~\|stNone]]~~ - does not synchronize. It will execute the callback	+	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:


−	~~[[Enum item SLTypes.TSLSynchronizeType.~~stQueue~~\|stQueue]]~~ - does synchronize and queue all the buffers with the	+	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:


−	~~[[Enum item SLTypes.TSLSynchronizeType.~~stSingleBuffer~~\|stSingleBuffer]]~~ - queues only the latest buffer. Any other	+	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 := ~~[[Enum item SLTypes.TSLSynchronizeType.~~stSingleBuffer~~\|stSingleBuffer]]~~;	+	SLGenericComplex1.SynchronizeType := stSingleBuffer;

	</code>		</code>
Line 43:		Line 43:

	<code>		<code>
−	SLGenericComplex1->SynchronizeType = ~~[[Enum item SLTypes.TSLSynchronizeType.~~stSingleBuffer~~\|stSingleBuffer]]~~;	+	SLGenericComplex1->SynchronizeType = stSingleBuffer;

	</code>		</code>
Line 49:		Line 49:

	<code>		<code>
−	SLGenericComplex1.SynchronizeType = ~~[[Enum item SLTypes.TSLSynchronizeType.~~stSingleBuffer~~\|stSingleBuffer]]~~;	+	SLGenericComplex1.SynchronizeType = stSingleBuffer;

	</code>		</code>

David Alm: Automated Syncronization with Documentation

2013-06-26T00:10:46Z

Automated Syncronization with Documentation

← Older revision		Revision as of 00:10, 26 June 2013
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>

David Alm: Automated Syncronization with Documentation

2013-06-26T00:10:07Z

Automated Syncronization with Documentation

← Older revision		Revision as of 00:10, 26 June 2013
Line 11:		Line 11:


−	~~[[Enum item SLTypes.TSLSynchronizeType.~~stNone~~\|stNone]]~~ - does not synchronize. It will execute the callback	+	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:


−	~~[[Enum item SLTypes.TSLSynchronizeType.~~stQueue~~\|stQueue]]~~ - does synchronize and queue all the buffers with the	+	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:


−	~~[[Enum item SLTypes.TSLSynchronizeType.~~stSingleBuffer~~\|stSingleBuffer]]~~ - queues only the latest buffer. Any other	+	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 := ~~[[Enum item SLTypes.TSLSynchronizeType.~~stSingleBuffer~~\|stSingleBuffer]]~~;	+	SLGenericComplex1.SynchronizeType := stSingleBuffer;

	</code>		</code>
Line 43:		Line 43:

	<code>		<code>
−	SLGenericComplex1->SynchronizeType = ~~[[Enum item SLTypes.TSLSynchronizeType.~~stSingleBuffer~~\|stSingleBuffer]]~~;	+	SLGenericComplex1->SynchronizeType = stSingleBuffer;

	</code>		</code>
Line 49:		Line 49:

	<code>		<code>
−	SLGenericComplex1.SynchronizeType = ~~[[Enum item SLTypes.TSLSynchronizeType.~~stSingleBuffer~~\|stSingleBuffer]]~~;	+	SLGenericComplex1.SynchronizeType = stSingleBuffer;

	</code>		</code>

David Alm: Automated Syncronization with Documentation

2013-06-25T23:52:34Z

Automated Syncronization with Documentation

← Older revision		Revision as of 23:52, 25 June 2013
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>

David Alm: Automated Syncronization with Documentation

2013-06-25T23:51:46Z

Automated Syncronization with Documentation

← Older revision		Revision as of 23:51, 25 June 2013
Line 11:		Line 11:


−	~~[[Enum item SLTypes.TSLSynchronizeType.~~stNone~~\|stNone]]~~ - does not synchronize. It will execute the callback	+	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:


−	~~[[Enum item SLTypes.TSLSynchronizeType.~~stQueue~~\|stQueue]]~~ - does synchronize and queue all the buffers with the	+	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:


−	~~[[Enum item SLTypes.TSLSynchronizeType.~~stSingleBuffer~~\|stSingleBuffer]]~~ - queues only the latest buffer. Any other	+	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 := ~~[[Enum item SLTypes.TSLSynchronizeType.~~stSingleBuffer~~\|stSingleBuffer]]~~;	+	SLGenericComplex1.SynchronizeType := stSingleBuffer;

	</code>		</code>
Line 43:		Line 43:

	<code>		<code>
−	SLGenericComplex1->SynchronizeType = ~~[[Enum item SLTypes.TSLSynchronizeType.~~stSingleBuffer~~\|stSingleBuffer]]~~;	+	SLGenericComplex1->SynchronizeType = stSingleBuffer;

	</code>		</code>
Line 49:		Line 49:

	<code>		<code>
−	SLGenericComplex1.SynchronizeType = ~~[[Enum item SLTypes.TSLSynchronizeType.~~stSingleBuffer~~\|stSingleBuffer]]~~;	+	SLGenericComplex1.SynchronizeType = stSingleBuffer;

	</code>		</code>

David Alm: Automated Syncronization with Documentation

2013-06-11T02:44:31Z

Automated Syncronization with Documentation

← Older revision		Revision as of 02:44, 11 June 2013
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>

David Alm: Automated Syncronization with Documentation

2013-06-11T02:43:54Z

Automated Syncronization with Documentation

← Older revision		Revision as of 02:43, 11 June 2013
Line 11:		Line 11:


−	~~[[Enum item SLTypes.TSLSynchronizeType.~~stNone~~\|stNone]]~~ - does not synchronize. It will execute the callback	+	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:


−	~~[[Enum item SLTypes.TSLSynchronizeType.~~stQueue~~\|stQueue]]~~ - does synchronize and queue all the buffers with the	+	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:


−	~~[[Enum item SLTypes.TSLSynchronizeType.~~stSingleBuffer~~\|stSingleBuffer]]~~ - queues only the latest buffer. Any other	+	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 := ~~[[Enum item SLTypes.TSLSynchronizeType.~~stSingleBuffer~~\|stSingleBuffer]]~~;	+	SLGenericComplex1.SynchronizeType := stSingleBuffer;

	</code>		</code>
Line 43:		Line 43:

	<code>		<code>
−	SLGenericComplex1->SynchronizeType = ~~[[Enum item SLTypes.TSLSynchronizeType.~~stSingleBuffer~~\|stSingleBuffer]]~~;	+	SLGenericComplex1->SynchronizeType = stSingleBuffer;

	</code>		</code>
Line 49:		Line 49:

	<code>		<code>
−	SLGenericComplex1.SynchronizeType = ~~[[Enum item SLTypes.TSLSynchronizeType.~~stSingleBuffer~~\|stSingleBuffer]]~~;	+	SLGenericComplex1.SynchronizeType = stSingleBuffer;

	</code>		</code>

David Alm: Automated Syncronization with Documentation

2013-06-11T00:15:23Z

Automated Syncronization with Documentation

← Older revision		Revision as of 00:15, 11 June 2013
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>

David Alm: Automated Syncronization with Documentation

2013-06-11T00:14:49Z

Automated Syncronization with Documentation

← Older revision		Revision as of 00:14, 11 June 2013
Line 11:		Line 11:


−	~~[[Enum item SLTypes.TSLSynchronizeType.~~stNone~~\|stNone]]~~ - does not synchronize. It will execute the callback	+	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:


−	~~[[Enum item SLTypes.TSLSynchronizeType.~~stQueue~~\|stQueue]]~~ - does synchronize and queue all the buffers with the	+	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:


−	~~[[Enum item SLTypes.TSLSynchronizeType.~~stSingleBuffer~~\|stSingleBuffer]]~~ - queues only the latest buffer. Any other	+	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 := ~~[[Enum item SLTypes.TSLSynchronizeType.~~stSingleBuffer~~\|stSingleBuffer]]~~;	+	SLGenericComplex1.SynchronizeType := stSingleBuffer;

	</code>		</code>
Line 43:		Line 43:

	<code>		<code>
−	SLGenericComplex1->SynchronizeType = ~~[[Enum item SLTypes.TSLSynchronizeType.~~stSingleBuffer~~\|stSingleBuffer]]~~;	+	SLGenericComplex1->SynchronizeType = stSingleBuffer;

	</code>		</code>
Line 49:		Line 49:

	<code>		<code>
−	SLGenericComplex1.SynchronizeType = ~~[[Enum item SLTypes.TSLSynchronizeType.~~stSingleBuffer~~\|stSingleBuffer]]~~;	+	SLGenericComplex1.SynchronizeType = stSingleBuffer;

	</code>		</code>