`VisuFbAnalyzeTextVarsDateTimeOnly` (FB)

FUNCTION_BLOCK VisuFbAnalyzeTextVarsDateTimeOnly EXTENDS VisuFbAnalyzeTextVars

Special derivation that simulates the behaviour of this function block on variables local to the IEC visu-lib code (and not on PLC variables)

InOut:

Scope	Name	Type	Initial	Comment	Inherited from
Input	`pVarText`	`Visu_TypeString`		to use this variable as text output variable needed for correct code generation this variable can have a conversion For the converted code we use a string member of a subclass of us. This subclass also has an instance variable, where the owning visual element instance can be stored CHECKED_OMIT	VisuFbAnalyzeTextVars
	`pTextConversion`	POINTER TO DWORD		needed for the integrated visu needed for CreateAnimationInstances the variable, this conversion belongs to as they both need to be in the same structure of fb we also define the order: VariableUsingConversion needs to be first. CHECKED_OMIT	VisuFbAnalyzeTextVars
	`diBitOffsetText`	`DINT`	-1	CHECKED_OMIT	VisuFbAnalyzeTextVars
	`pVarTooltip`	`Visu_TypeString`		needed for correct code generation this variable can have a conversion CHECKED_OMIT	VisuFbAnalyzeTextVars
	`pTooltipConversion`	POINTER TO DWORD		needed for the integrated visu needed for CreateAnimationInstances the variable, this conversion belongs to CHECKED_OMIT	VisuFbAnalyzeTextVars
	`diBitOffsetTooltip`	`DINT`	-1	CHECKED_OMIT	VisuFbAnalyzeTextVars
	`dwVarTextType`	`DWORD`			VisuFbAnalyzeTextVars
	`dwVarTooltipType`	`DWORD`			VisuFbAnalyzeTextVars
	`wTextVarValid`	`WORD`		set according to used Variables	VisuFbAnalyzeTextVars
	`pTextListName`	POINTER TO STRING		the textlistname is always generated as string @IECCodeConverter_Type: String	VisuFbAnalyzeTextVars
Inout	`_EffectiveTexts`	`VisuStructElementTexts`		evtl. as Parameter to Method Execute	VisuFbAnalyzeTextVars
	`pBuffer`	POINTER TO BYTE			VisuFbAnalyzeTextVars
	`dwBufferSize`	`DWORD`			VisuFbAnalyzeTextVars

VisuFbAnalyzeTextVarsDateTimeOnly (FB)

`VisuFbAnalyzeTextVarsDateTimeOnly` (FB)