Defining a Program in a Folder on the Desktop

Use the WPObject structure to define a folder or a program (to be added to a folder). The WPObject structure calls the OS/2 WinCreateObject function, which adds an icon and title to the desktop. This structure indirectly changes the OS2.INI file. Refer to the OS/2 Presentation Manager Guide and Reference for object class definitions and supported keywords for the object class you are creating.

Use the WPObject structure shown in the following example to define a folder.

WPObject =
    (
    WPClassName   = "WPFolder"
    WPTitle       = "title"
    WPSetupString = "ICONFILE=$(DEST)icon;OBJECTID=<folderobjid>"
    WPLocation    = "<parentfolderobjid>"
    WPFlags       = wpflags
    )

title

Specifies the folder title to be displayed below the object.
icon
Specifies the file name of the icon representing the object.
<folderobjid>
Specifies the OS/2 unique object ID that is used to find this folder. This is used by the Workplace Shell to determine if this folder exists or not. It is also used in the WPLocation field of other WPObject definitions.
<parentfolderobjid>
Specifies the folder object ID of the folder in which this folder is to be placed. For example, "<WP_DESKTOP>" is the object ID for the Workplace Shell Desktop folder.
wpflags
This value specifies what action is to be taken if the object already exists.
• Fail if the object exists.

• Replace the object if it exists.

• Update the object if it exists (change the specified fields to the given values).

In the following example, a folder called Multimedia Presentation Manager Toolkit/2 will be added to the desktop.

WPObject =    (
    WPClassName   = "WPFolder"
    WPTitle       = "Multimedia Presentation\nManager Toolkit/2"
    WPSetupString = "ICONFILE=$(DEST)MMTOOLKT.ICO;OBJECTID=<MMPMTLK>"
    WPLocation    = "<WP_DESKTOP>"
    WPFlags       = 2L
    )

You can also use the WPObject structure to define a program that will be added to a folder on the desktop as shown in the following figure.

WPObject =
(
WPClassName   = "WPProgram"
WPTitle       = "title"
WPSetupString = "EXENAME=path file;STARTUPDIR =dir;PROGTYPE=PM;
     ICONFILE=$(DEST)icon; [ASSOCTYPE =type;]
     [ASSOCFILTER=filter;] OBJECTID=<pgmobjid>"
WPLocation    = "<parentfolderobjid>"
WPFlags       = wpflags
)

title

Specifies the title to be displayed below the object in the parent folder.
path
Specifies a supported macro or the full path for the EXE file.
file
Specifies the EXE file name.
dir
Specifies the full path of the startup directory or the macro $(DIR)# (where # is a defined destination directory in CONTROL.SCR).
icon
Specifies the file name of the icon representing the object.
type
Specifies one or more association types such as "Waveform." Multiple values are separated by commas.
filter
Specifies one or more association filter types such as "*.WAV." Multiple values are separated by commas.
<pgmobjid>
Specifies the OS/2 unique object ID that is used to find this program. This is used by the installation program to determine if this program exists in the parent folder. It is not used in the WPLocation field of any WPObject definition.
<parentfolderobjid>
Specifies the folder object ID of the folder in which this program is to be placed.
wpflags
This value specifies what action is to be taken if the object already exists.
• Fail if the object exists.

• Replace the object if it exists.

• Update the object if it exists (change the specified fields to the given values).
JoinEA Structure

The JoinEA structure shown in the following example causes the joining of an EA file to the parent file or directory. If the file or directory is used in a WPObject declaration, this structure should precede that declaration.

JoinEA =
    (
    JoinFileName   = "full path to file"
    JoinEAFileName = "full path to EA file"
    )

full path to file

Specifies the full path to this file. Supported macros may be used.
full path to EA file
Specifies the full path to the EA file. Supported macros may be used.
JoinLongNameEA Structure

The JoinLongNameEA structure shown in the following example allows you to specify a name that is greater than the standard 8-character length for a directory you are going to create as a Workplace Shell object. The JoinLongNameEA statement causes an EA file of type LONGNAME to be added to the directory. The long name is then displayed whenever the directory appears as a folder object. The JoinLongNameEA statement should come before creating the directory as a Workplace Shell object.

JoinLongNameEA =
    (
    JoinLongName       = "longname"
    JoinLongFileName   = "full path to directory"
    JoinEALongFileName = "full path to EA file"
    )

longname

Specifies the new long name to be displayed.
full path to directory
Specifies the directory to which EAs are to be attached. Supported macros may be used.
full path to EA file
Specifies the full path to the EA file. Supported macros may be used.

Following is an example of a long name specified for an OS/2 multimedia directory with the JoinLongNameEA structure. The long name "Sound Bites" is added to the directory defined as "9" in the CONTROL.SCR file. In this case, it is the "Sounds" directory.

JoinLongNameEA =    (
    JoinLongName       = "Sound Bites"
    JoinLongFileName   = "$(DIR)9"
    JoinEALongFileName = "$(DRIVE):\\MMOS2\\INSTALL\\sounds.eas"
    )

The $(DEST) macro is not used for this structure because the file is created, not copied and changed by MINSTALL. Notice that the file is placed in the \MMOS2\INSTALL subdirectory. This is the directory to which all EAs should be copied.

---

[Back: INI Change Control Files]
[Next: Defining Changes to the MMPM2.INI File]