Resource Container - Revision history

Flarn2006: /* Known Resources */ Added another VITS example

2022-02-09T03:19:54Z

Known Resources: Added another VITS example

← Older revision		Revision as of 03:19, 9 February 2022
Line 372:		Line 372:
	\|VITS		\|VITS
	\|Virtual Instrument Tag Strings		\|Virtual Instrument Tag Strings
	\|Contains a VI's persistent tags. Tags are additional data which is attached to a VI and manipulated using [[VI Server#Private\|private methods]] such as [[VI class/Tag.Set Tag\|VI class/Tag.Set Tag]] on the VI object. Certain tags can affect LabVIEW's functionality; for example, the ~~built-in~~ matrix typedefs~~' "operator overloading" effect is caused by~~ a ~~tag named~~ "NI.LV.All.OperatorInfo1" in the ~~.ctl files~~.		\|Contains a VI's persistent tags. Tags are additional data which is attached to a VI and manipulated using [[VI Server#Private\|private methods]] such as [[VI class/Tag.Set Tag\|VI class/Tag.Set Tag]] on the VI object. Certain tags can affect LabVIEW's functionality; for example, [[Express VI]] source VI's have a "_Wizard" tag containing the path to the configuration dialog VI, and the matrix typedefs contain a "NI.LV.All.OperatorInfo1" tag which configures the special "operator overloading" effect they have.
	\|}		\|}

	[[Category:LabVIEW file extensions\|other files]]		[[Category:LabVIEW file extensions\|other files]]
	[[Category:LabVIEW internals]]		[[Category:LabVIEW internals]]

Flarn2006: added FPTS and BDTS

2022-02-09T03:17:49Z

added FPTS and BDTS

← Older revision		Revision as of 03:17, 9 February 2022
Line 21:		Line 21:
	\|Front Panel Size Estimate		\|Front Panel Size Estimate
	\|Optional resource which can be used to optimize memory allocation when loading the VI file. Contains one integer value, which seem be amount of tags within Front Panel Heap divided by 10. See also: ''BDSE''.		\|Optional resource which can be used to optimize memory allocation when loading the VI file. Contains one integer value, which seem be amount of tags within Front Panel Heap divided by 10. See also: ''BDSE''.
			\|-
			\|FPTS
			\|Front Panel Tags
			\|Contains data for tags set on front panel objects using the [[Generic class/Tag.Get Tag method\|Get Tag]] method.
	\|-		\|-
	\|FPTD		\|FPTD
Line 29:		Line 33:
	\|Block Diagram Size Estimate		\|Block Diagram Size Estimate
	\|Optional resource which can be used to optimize memory allocation when loading the VI file. Contains one integer value, which seem be amount of tags within Block Diagram Heap divided by 10. See also: ''FPSE''.		\|Optional resource which can be used to optimize memory allocation when loading the VI file. Contains one integer value, which seem be amount of tags within Block Diagram Heap divided by 10. See also: ''FPSE''.
			\|-
			\|BDTS
			\|Block Diagram Tags
			\|Contains data for tags set on block diagram objects using the [[Generic class/Tag.Get Tag method\|Get Tag]] method.
	\|-		\|-
	\|FLAG		\|FLAG

Flarn2006: Added .rsc extension

2022-01-28T22:39:25Z

Added .rsc extension

← Older revision		Revision as of 22:39, 28 January 2022
Line 1:		Line 1:
	'''Resource Container''' file format is a most often used file format within LabVIEW ecosystem. It is a proprietary binary format defined by [[National Instruments]] and used in both [[LabVIEW]] and [https://en.wikipedia.org/wiki/LabWindows/CVI LabWindows/CVI]. The format is strongly inspired by [https://en.wikipedia.org/wiki/Resource_fork Mac OS Resource Fork format], as LabVIEW was originally created for that platform, and ported to other OSes later, at [[LabVIEW 2.0\|version 2.5]].		'''Resource Container''' file format is a most often used file format within LabVIEW ecosystem. It is a proprietary binary format defined by [[National Instruments]] and used in both [[LabVIEW]] and [https://en.wikipedia.org/wiki/LabWindows/CVI LabWindows/CVI]. The format is strongly inspired by [https://en.wikipedia.org/wiki/Resource_fork Mac OS Resource Fork format], as LabVIEW was originally created for that platform, and ported to other OSes later, at [[LabVIEW 2.0\|version 2.5]].

	The format is a container, storing a group of '''Resources'''. Resources have '''4-character identifier''' assigned, and the 4-character identifier for the whole container is ''RSRC''. Most files used by LabVIEW have that ''RSRC'' format, only the specific '''Resources''' stored inside are different. The files with that header include [[VI File Extension\|''.vi'']], [[CTL File Extension\|''.ctl'']], [[MNU File Extension\|''.mnu'']], [[LLB File Extension\|''.llb'']], [[DLOG File Extension\|''.dlog'']], [[CTT File Extension\|''.ctt'']], [[VIT File Extension\|''.vit'']], [[UIR File Extension\|''.uir'']], and many created with, or internally used by, LabVIEW.		The format is a container, storing a group of '''Resources'''. Resources have '''4-character identifier''' assigned, and the 4-character identifier for the whole container is ''RSRC''. Most files used by LabVIEW have that ''RSRC'' format, only the specific '''Resources''' stored inside are different. The files with that header include [[VI File Extension\|''.vi'']], [[CTL File Extension\|''.ctl'']], [[MNU File Extension\|''.mnu'']], [[LLB File Extension\|''.llb'']], [[DLOG File Extension\|''.dlog'']], [[CTT File Extension\|''.ctt'']], [[VIT File Extension\|''.vit'']], [[UIR File Extension\|''.uir'']], [[RSC File Extension\|''*.rsc'']], and many created with, or internally used by, LabVIEW.

	The resources stored within have their identifiers often identical to those in ''Resource fork'' format, but many new ones are also introduced. Some resources have multiple variations, as their structure changed between versions of [[LabVIEW]].		The resources stored within have their identifiers often identical to those in ''Resource fork'' format, but many new ones are also introduced. Some resources have multiple variations, as their structure changed between versions of [[LabVIEW]].

Flarn2006: Added VCTP compression details

2022-01-28T22:38:11Z

Added VCTP compression details

← Older revision		Revision as of 22:38, 28 January 2022
Line 356:		Line 356:
	\|VCTP		\|VCTP
	\|VI Consolidated Data Types		\|VI Consolidated Data Types
	\|Introduced in LV 8.0, stores all [[Type descriptor\|Type descriptors]] used within the file.		\|Introduced in LV 8.0, stores all [[Type descriptor\|Type descriptors]] used within the file. Consists of a Zlib-compressed data block preceded by four bytes containing the length of the compressed data in big-endian.
	\|-		\|-
	\|VICD		\|VICD

Flarn2006: /* Known Resources */ Added more VITS details

2022-01-28T01:33:03Z

Known Resources: Added more VITS details

← Older revision		Revision as of 01:33, 28 January 2022
Line 364:		Line 364:
	\|VITS		\|VITS
	\|Virtual Instrument Tag Strings		\|Virtual Instrument Tag Strings
	\|~~This section~~ is ~~responsible~~ for the "operator overloading" effect ~~that the built-in matrix typedefs have~~. ~~Copying it from RealMatrix~~.~~ctl to a new typedef, and then wiring an instance of that new typedef to an Add node, causes the Add node to become its matrix variant, as occurs with~~ the ~~matrix typedef~~. ~~This section is most likely used for other purposes as well~~.		\|Contains a VI's persistent tags. Tags are additional data which is attached to a VI and manipulated using [[VI Server#Private\|private methods]] such as [[VI class/Tag.Set Tag\|VI class/Tag.Set Tag]] on the VI object. Certain tags can affect LabVIEW's functionality; for example, the built-in matrix typedefs' "operator overloading" effect is caused by a tag named "NI.LV.All.OperatorInfo1" in the .ctl files.
	\|}		\|}

	[[Category:LabVIEW file extensions\|other files]]		[[Category:LabVIEW file extensions\|other files]]
	[[Category:LabVIEW internals]]		[[Category:LabVIEW internals]]

Flarn2006: Added BDHT/FPHT/BDHX/FPHX

2020-09-20T17:24:49Z

Added BDHT/FPHT/BDHX/FPHX

@@ Line 313: / Line 313: @@
 |Front Panel Heap ver c
 |Third version of [[Heap storage format]], used to store components placed on Front Panel.
 |-
 |RTSG

Flarn2006: /* Known Resources */ Added an observed effect of VITS (operator overloading)

2020-09-20T17:19:52Z

Known Resources: Added an observed effect of VITS (operator overloading)

← Older revision		Revision as of 17:19, 20 September 2020
Line 348:		Line 348:
	\|VITS		\|VITS
	\|Virtual Instrument Tag Strings		\|Virtual Instrument Tag Strings
	\|		\|This section is responsible for the "operator overloading" effect that the built-in matrix typedefs have. Copying it from RealMatrix.ctl to a new typedef, and then wiring an instance of that new typedef to an Add node, causes the Add node to become its matrix variant, as occurs with the matrix typedef. This section is most likely used for other purposes as well.
	\|}		\|}

	[[Category:LabVIEW file extensions\|other files]]		[[Category:LabVIEW file extensions\|other files]]
	[[Category:LabVIEW internals]]		[[Category:LabVIEW internals]]

Mefistotelis: heaps commented

2020-06-10T14:42:25Z

heaps commented

← Older revision		Revision as of 14:42, 10 June 2020
Line 292:		Line 292:
	\|BDHP		\|BDHP
	\|Block Diagram Heap		\|Block Diagram Heap
	\|		\|First version of [[Heap storage format]], used to store components placed on Block Diagram.
	\|-		\|-
	\|FPHP		\|FPHP
	\|Front Panel Heap		\|Front Panel Heap
	\|		\|First version of [[Heap storage format]], used to store components placed on Front Panel.
	\|-		\|-
	\|BDHb		\|BDHb
	\|Block Diagram Heap ver b		\|Block Diagram Heap ver b
	\|		\|Second version of [[Heap storage format]], used to store components placed on Block Diagram.
	\|-		\|-
	\|FPHb		\|FPHb
	\|Front Panel Heap ver b		\|Front Panel Heap ver b
	\|		\|Second version of [[Heap storage format]], used to store components placed on Front Panel.
	\|-		\|-
	\|BDHc		\|BDHc
	\|Block Diagram Heap ver c		\|Block Diagram Heap ver c
	\|		\|Third version of [[Heap storage format]], used to store components placed on Block Diagram.
	\|-		\|-
	\|FPHc		\|FPHc
	\|Front Panel Heap ver c		\|Front Panel Heap ver c
	\|		\|Third version of [[Heap storage format]], used to store components placed on Front Panel.
	\|-		\|-
	\|RTSG		\|RTSG

Mefistotelis: refs

2020-06-05T07:15:55Z

refs

← Older revision		Revision as of 07:15, 5 June 2020
Line 1:		Line 1:
	'''Resource Container''' file format is a most often used file format within LabVIEW ecosystem. It is a proprietary binary format defined by [[National Instruments]] and used in both [[LabVIEW]] and LabWindows. The format is strongly inspired by [https://en.wikipedia.org/wiki/Resource_fork Mac OS Resource Fork format], as LabVIEW was originally created for that platform, and ported to other OSes later, at version 2.5.		'''Resource Container''' file format is a most often used file format within LabVIEW ecosystem. It is a proprietary binary format defined by [[National Instruments]] and used in both [[LabVIEW]] and [https://en.wikipedia.org/wiki/LabWindows/CVI LabWindows/CVI]. The format is strongly inspired by [https://en.wikipedia.org/wiki/Resource_fork Mac OS Resource Fork format], as LabVIEW was originally created for that platform, and ported to other OSes later, at [[LabVIEW 2.0\|version 2.5]].

	The format is a container, storing a group of '''Resources'''. Resources have '''4-character identifier''' assigned, and the 4-character identifier for the whole container is ''RSRC''. Most files used by LabVIEW have that ''RSRC'' format, only the specific '''Resources''' stored inside are different. The files with that header include [[VI File Extension\|''.vi'']], [[CTL File Extension\|''.ctl'']], [[MNU File Extension\|''.mnu'']], [[LLB File Extension\|''.llb'']], [[DLOG File Extension\|''.dlog'']], [[CTT File Extension\|''.ctt'']], [[VIT File Extension\|''.vit'']], [[UIR File Extension\|''.uir'']], and many created with, or internally used by, LabVIEW.		The format is a container, storing a group of '''Resources'''. Resources have '''4-character identifier''' assigned, and the 4-character identifier for the whole container is ''RSRC''. Most files used by LabVIEW have that ''RSRC'' format, only the specific '''Resources''' stored inside are different. The files with that header include [[VI File Extension\|''.vi'']], [[CTL File Extension\|''.ctl'']], [[MNU File Extension\|''.mnu'']], [[LLB File Extension\|''.llb'']], [[DLOG File Extension\|''.dlog'']], [[CTT File Extension\|''.ctt'']], [[VIT File Extension\|''.vit'']], [[UIR File Extension\|''.uir'']], and many created with, or internally used by, LabVIEW.

Mefistotelis: added refs

2020-06-02T10:11:04Z

added refs

← Older revision		Revision as of 10:11, 2 June 2020
Line 192:		Line 192:
	\|DSTM		\|DSTM
	\|Data Space Type Map		\|Data Space Type Map
	\|Stores table of [[Type descriptor\|Type descriptors]] which make up Data Space of the VI file. Used in LV 7.1 and older.		\|Stores table of [[Type descriptor\|Type descriptors]] which make up [[Data Space]] of the VI file. Used in LV 7.1 and older.
	\|-		\|-
	\|TM80		\|TM80
	\|Data Space Type Map LV8.0+		\|Data Space Type Map LV8.0+
	\|Stores table of references to [[Type descriptor\|Type descriptors]] which make up Data Space of the VI file. The actual definitions of '''TD'''s are stored in ''VCTP'' block. Used in LV 8.0 and newer.		\|Stores table of references to [[Type descriptor\|Type descriptors]] which make up [[Data Space]] of the [[VI\|VI file]]. The actual definitions of '''TD'''s are stored in ''VCTP'' block. Used in [[LabVIEW 8\|LV 8.0]] and newer.
	\|-		\|-
	\|LVIN		\|LVIN
	\|LabView Instrument		\|LabView Instrument
	\|General information about a saved VI file; definitely used in LV 4.0 and older, was replaced by ''LVSR'' at some point.		\|General information about a saved [[VI\|VI file]]; definitely used in [[LabVIEW 4.0\|LV 4.0]] and older, was replaced by ''LVSR'' at some point.
	\|-		\|-
	\|LVSR		\|LVSR
	\|LabView Save Record		\|LabView Save Record
	\|General information about a saved VI file; replaced ''LVIN'' resource somewhere before LV 6.0. The size of this resource increases with LV version, but old data is always kept at the same offset (new fields are only added at end).		\|General information about a saved [[VI\|VI file]]; replaced ''LVIN'' resource somewhere before [[LabVIEW 6i\|LV 6.0]]. The size of this resource increases with [[LabVIEW Versions\|LV version]], but old data is always kept at the same offset (new fields are only added at end).
	\|-		\|-
	\|vers		\|vers