[Contents] [Index] [Help] [Retrace] [Browse <] [Browse >]

Data properties specify attributes for following (non-property) chunk.  A
data property essentially says "identifier = value", for example "XY =
(10, 200)", telling something about following chunks.  Properties may only
appear inside data sections ("FORM" chunks, cf. Data Sections) and
property sections ("PROP" chunks, cf. Group PROP).

The form of a data property is a type of Chunk.  The ckID is a property
name as well as a property type.  The ckSize should be small since data
properties are intended to be accumulated in RAM when reading a file.
(256 bytes is a reasonable upper bound.)  Syntactically:

	Property	::= Chunk

When designing a data object, use properties to describe context
information like the size of an image, even if they don't vary in your
program.  Other programs will need this information.

Think of property settings as assignments to variables in a programming
language.  Multiple assignments are redundant and local assignments
temporarily override global assignments.  The order of assignments doesn't
matter as long as they precede the affected chunk.  (Cf. LISTs, CATs, and
Shared Properties.)

Each object type (FORM type) is a local name space for property IDs.
Think of a "CMAP" property in a "FORM ILBM" as the qualified ID
"ILBM.CMAP".  A "CMAP" inside some other type of FORM may not have the
same meaning.  Property IDs specified when an object type is designed (and
therefore known to all clients) are called "standard" while specialized
ones added later are "nonstandard".

[Back to Amiga Developer Docs]