User-Defined Resources

An application can also define its own resource. The resource can be any data that the application intends to use. A user-defined resource statement has the form:

 ───resource-type───typeID───nameID────────────────────────────

 ────┬──────────────┬───┬─────────────┬───filename────
      └──loadoption──┘   └──memoption──┘

typeID

Either a unique name or an integer number identifying the resource type. If a number is given, it must be greater than 255. The type numbers 1 through 255 are reserved for existing and future predefined resource types. Value 1000 is reserved for custom fonts.
nameID
Either a unique name or an integer number identifying the resource.
loadoption (LOADOPTION)
The default is LOADONCALL.

See Resource Load and Memory Options for a description of LOADOPTION.

memoption (MEMOPTION)
The default is MOVEABLE.

See Resource Load and Memory Options for a description of MEMOPTION.

filename
Can be either:

• An ASCII string specifying the OS/2* name of the file containing the cursor bit map. A full path must be given if the file is not in the current working directory.

• A BEGIN END data definition construct as follows:

  BEGIN
  data-definition [, data-definition] ...
     .
     .
     .
  END
  

  For example, the RESOURCE statement might be written as follows:

  RESOURCE MYRES "array"
  BEGIN
    13L, 26L
  END
  

When the resource compiler (RC.EXE) encounters one or more font resources, or any custom resource having type-id of 1000, it creates a font directory resource which it adds to the output binary data.

Example

RESOURCE MYRES   "array" DATA.RES
RESOURCE 300     14      CUSTOM.RES

---

[Back: Single-Line Statements]
[Next: RCDATA statement]