═══ 1. About ObjectSpy ═══ The ObjectSpy... ═══ 2. ObjectSpy General Page ═══ General page. Object Title is the object title as it appears below its icon. Object Class is the name of the WPS class the target object is an instance of. DLL Name is the name of the dynamic link library that contains the definition for the object's class. Object ID is a unique identifier for the object. Identifiers are not mandatory. If the object has no id, this field will be blank. Object Location is the id of the folder that contains the object. If the folder has no id, this field will contain the full path name of the folder. The Class Hierarchy view presents the inheritance tree for the object's class, with the object's class at the bottom of the hierarchy. Icon shows the icon of the object. The Object Views group contains three buttons that perform different actions on the target object: The Open button opens the default view for the object, as if you would have double-clicked on its icon. The Settings button opens the settings notebook for the object. The Help button brings up the default help panel for the object, if any. If no help is available, a message stating that condition will be displayed. The Help button at the bottom of the page activates the help for this page (not to be confused with the Help button in the Object Views group). ═══ 3. ObjectSpy Styles Page ═══ Styles Page. This page presents the object styles by the means of check boxes, so the user can change the settings if desired. Following is a brief explanation for each style: Style Description No Move If checked, the object cannot be moved; there is no Move option in the object's context menu. No Link If checked, this object cannot have shadows; there is no Create Shadows option in the object's context menu. No Copy If checked, this object cannot be copied; there is no Copy option in the object's context menu. No Default Icon If checked, the icon associated with this object is not the class default icon. This item is for information only, so it appears deselected. Note: This style cannot be changed, because it is used by the Workplace Shell and, if set incorrectly, can cause the object's icon to disappear or not to be freed when necessary. Template If checked, this object is a template. No Delete If checked, the object cannot be deleted; the object cannot be dragged to the shredder and there is no Delete option in the object's context menu. No Print If checked, the object cannot be printed; there is no Print option in the object's context menu and the object cannot be dragged onto a Printer object. No Drag If checked, the object cannot be moved, copied or dragged; there are no Copy, Move or Pickup options in the object's context menu. Not Visible If checked, the object becomes invisible. No Settings If checked, this object cannot be opened in settings view; there is no Settings option in the object's context menu. No Rename If checked, the object cannot be renamed; its title cannot be changed either by editing the string under the icon or by changing it on the General page of the Settings notebook. No Drop If checked, no other object can be dropped on this object. After making the desired changes, press the Apply button so that the changes can take effect. The Undo button will undo any changes made since the last Apply. Warning: Care should be taken when using this feature, since some changes may be difficult or impossible to undo. For example, if you set the Not Visible and/or No Drag styles and close the ObjectSpy notebook for the object, you won't be able to reset these styles with ObjectSpy. You can however experiment with these styles while keeping the notebook open, so you can reset them when finished. ═══ 4. ObjectSpy ObjectSetup Page ═══ Setup String page. This page allows the user to specify and apply setup strings for the target object. The user can select from the lists of predefined key names and values or can enter his own key name-value pairs in the entry fields provided. By moving the selection bar in the Keynames list box, the values corresponding to the selected key will appear in the Values box. There are two types of values: predefined, that appear in the value list as uppercase strings, and user-supplied values, for which the value list will display a template string. The template string consists of lowercase identifiers that suggest the type of data expected, enclosed or delimited by special characters that must be part of the value. To select a key-value pair, double-click on the desired value item; the corresponding keyname will fill the Keyname entry field; if the selected value is a predefined one, it will fill the Value entry field; otherwise, the Value entry field will gain the input focus so that the user can enter the value according to the template string. To enter your own key-value pair, double-click on the last item in the Keynames list box: "other". Now you can enter the key name in the Keyname entry field, then move to the Value field to enter the value. The values for most keys are mutually exclusive, but there are a few keys that allow the selection of more than one value; in that case, the selected values will be added to the value string, delimited by commas. This is where the Clear Value button might become handy because it clears the value entry field and allows user to select a new set of values if desired. Once the Keyname and Value entry fields have been filled, the pair can be added to the Setup String list at the top of the page by pressing the Add to String button. Now let's take a closer look at the Setup String group it consists of a list box containing all the setup strings that were added thru the process described above, and a set of buttons. The Delete Selected button removes the selected string from the setup list. The Clear button will clear the setup list. The Apply button attempts to apply the setup strings in the list to the target object; the strings that have been successfully applied are removed from the list; the ones for which the setup fail remain in the list as an indication to the user. See also: Predefined Keynames and Values ═══ 5. ObjectSpy Details Data Page ═══ Details Data Page. Details data are part of an object instance data and define more accurately the characteristics and behavior of the object. They are displayed in the folder details view and can be used to define include, find and sort criteria. The details view for a folder includes only those detail fields that were set for that folder, by default the ones defined by WPFileSystem class. For heterogeneous folders (containing different types of objects), this may not be appropriate. The Details Data page displays all the details data for the target object, both those inherited from the ancestor classes and the ones defined by the object's class (if any). The details data are presented in a two-column container window; the first column contains the details fields names, the second column contains the corresponding data value. ═══ 6. ObjectSpy Methods Page ═══ Methods page. This page displays in a list box all the methods for the target object, defined by the object's class and inherited, public and private, static and dynamic. The Methods list contains the names of the methods preceded by the name of the class that defined the method. To view the signature of a method, place the selection bar over it and press Syntax. The method's signature will appear in the Syntax box in the following form: ([]); where is the list of methods parameters separated by commas: = [, [,...] ] and: = For some methods instead of signature you may get the message: "unknown signature" This means that there are no information for that method in the interface repository files which ObjectSpy searches to find the method's signature. Note: Searching interface repository files may sometimes be a time-consuming operation and the thread that searches for method signatures may not have finished by the time you've reached the Methods page. In that case, the syntax box will display the message: "Searching interface repository..." and the Syntax button will appear disabled. The message will go away and the Syntax button enabled as soon as the signature information becomes available. ═══ 7. ObjectSpy Extended Attributes Page ═══ Extended Attributes page. Besides the basic information describing files like name, size, date and time for file creation and last access operations, OS/2 enables applications to attach additional information to a file object in the form of extended attributes (EAs). Extended attributes are used to describe the file object to another application, the operating system, and to the file system that manages the object. Each extended attribute has a name and a value. The name is a ASCII string; the value can be anything at all. It is the responsibility of the application that creates and/or uses the EA to recognize the format and meaning of the data associated with a given EA name. However, so that applications can understand the type of information stored in an EA, the first word of EA's data must specify one of the following data types: ┌────────┬────────────────────┐ │EAT_BINA│Binary data │ ├────────┼────────────────────┤ │EAT_ASCI│ASCII text │ ├────────┼────────────────────┤ │EAT_BITM│Bitmap data │ ├────────┼────────────────────┤ │EAT_META│Metafile data │ ├────────┼────────────────────┤ │EAT_ICON│Icon data │ ├────────┼────────────────────┤ │EAT_EA │ASCII name of │ │ │another EA that is │ │ │associated with the │ │ │file. │ ├────────┼────────────────────┤ │EAT_MVMT│Multi-valued, │ │ │multi-typed data - │ │ │two or more │ │ │consecutive extended│ │ │attribute values, of│ │ │different types. │ ├────────┼────────────────────┤ │EAT_MVST│Multi-valued, │ │ │single-typed data - │ │ │two or more │ │ │consecutive extended│ │ │attribute values of │ │ │the same type. │ ├────────┼────────────────────┤ │EAT_ASN1│ANS.1 ISO standard │ │ │is used to describe │ │ │a multi-valued data │ │ │stream. │ └────────┴────────────────────┘ The Extended Attributes Page displays the extended attributes for the target object. The values and meaning for the "type" column are as follows: ┌───────────────┬──────────────────────────────┐ │BIN │Binary data │ ├───────────────┼──────────────────────────────┤ │TEXT │ASCII text │ ├───────────────┼──────────────────────────────┤ │BMP │Bitmap data │ ├───────────────┼──────────────────────────────┤ │MET │Metafile data │ ├───────────────┼──────────────────────────────┤ │ICON │Icon data │ ├───────────────┼──────────────────────────────┤ │EA │ASCII name of another EA that │ │ │is associated with the file. │ ├───────────────┼──────────────────────────────┤ │MVMT │Multi-valued, multi-typed data│ ├───────────────┼──────────────────────────────┤ │MVST │Multi-valued, single-typed │ │ │data │ ├───────────────┼──────────────────────────────┤ │ASN1 │ANS.1 ISO standard │ └───────────────┴──────────────────────────────┘ The length field contains the length in bytes of the EA data, except for the multi-valued fields when it contains the number of data items; in that case, the actual items are displayed on the following lines. The data field displays the actual data for text items. ═══ 8. ObjectSpy Interface Page ═══ Interface Repository page. This page displays the interface definition for the target object's class using the Interface Definition Language (SOM IDL) syntax. The interface definition is displayed in a list box. You can browse through the list using the scroll bars or you can print its content by pressing the Print button. The definition begins with an "interface" statement that specifies the target class name followed by the name(s) of its parent(s). The body of the definition can contain type, constant, attribute, method and exception declarations, followed by an implementation statement. The type declarations are preceded by the typedef keyword and are similar to the C/C++ language typedefs. The constant declarations are preceded by the const keyword and are similar to the const declarations in C/C++; The attribute declarations consist of the attribute keyword followed by the type and name of the attribute; sometimes the attribute declaration may be preceded by the readonly keyword, indicating that the attribute value can be accessed but not modified by client programs (the attribute has no "set" method). The method declarations define the signature for each method introduced by the class; the syntax is similar to the one presented in the previous chapter (the Methods page) with one addition: the parameter declarations in the parameter list are preceded by one of the following three directional attributes: in | out | inout indicating whether the parameter is to be passed from client to server (in), from server to client (out) or in both directions. The exception declarations consist of the exception keyword followed by the name of the exception and,optionally, a list of members enclosed in curly brackets; a member declaration has the following form: ; where is a valid IDL type and is an identifier. An interface definition may contain an implementation stteament. The implementation statement has the following form: implementation { modifier statements }; A modifier statement gives additional implementation information about interface, attribute, method and/or type definitions. A modifier can be unqualified or qualified. A unqualified modifier is associated with the interface it is defined in and can have the following two forms: modifier; modifier = value; where can be a predefined or user-defined identifier and is an identifier, string enclosed in double quotes or a number. A qualified modifier is associated with a qualifier and can have the following two forms: qualifier : modifier; qualifier : modifier = value; where is the identifier of a IDL definition or is user defined. For more information on Interface Definition Language refer to your SOM Developer Toolkit documentation. For some classes instead of the interface definition you may get the message: "No interface repository information for " This means that ObjectSpy found no entry for the specified class in the in the interface repository files specified by the SOMIR environment variable. Note: The search for the interface information may take some time and the thread that performs the search may not have finished by the time you've reached the Interface page. In that case, the interface box will display the message: "Searching interface repository..." and the Print button will appear disabled. The message will go away and the Print button enabled as soon as the interface information becomes available. ═══ 9. ObjectSpy Class Info Page ═══ Class Info page. The list box in the center of the page contains the current WPS class hierarchy. To add a new class to this hierarchy, press the Add button. See Add New Class Dialog. The rest of the buttons at the bottom of the page allow the user to perform operations on a selected class: delete, instantiate, replace, unreplace, view interface definition. Delete class Select the class to be deleted from the class list, then press the Delete button. A message box will appear asking user to confirm the deletion of the selected class. If the user agrees, the class will be deregistered and removed from the class list. Create instance Select the class to instantiate from the class list, then press the Instance button. See Create Instance Dialog. Replace class Select the class to be replaced from the class list, then press the Replace button. See Replace Class Dialog. Unreplace class Select the class to be unreplaced from the class list, then press the Unreplace button. See UnReplace Class Dialog View interface definition Select the desired class from the class list, then press the Interface button. See Interface Definition Dialog. ═══ 10. Add New Class Dialog ═══ Add New Class Dialog Enter the new class name, and the name of the DLL that contains the class definition in the entry fields provided, then press Ok to add the class; press Cancel to abort the operation and return to the Class Info page. ═══ 11. Create Instance Dialog ═══ Create Instance Dialog The Class Name entry field is set to the selected class name. Enter the object title, location and, optionally, the setup string in the designated entry fields and press Ok to create the instance; press Cancel to abandon the operation. ═══ 12. Replace Class Dialog ═══ Replace Class Dialog The Original Class Name entry field is set to the selected class name. Enter the replacement class name and press Ok to replace the class; press Cancel to abandon the operation. ═══ 13. Unreplace Class Dialog ═══ Unreplace Class Dialog The Original Class Name entry field is set to the selected class name. Enter the replacement class name and press Ok to unreplace the class; press Cancel to abandon the operation. ═══ 14. Interface Definition Dialog ═══ Interface Definition Dialog This dialog displays the interface definition for the selected class using the Interface Definition Language (SOM IDL) syntax. The message: "Searching interface repository..." will be replaced by the interface definition for the selected class as soon as that information becomes available; then the Print button will be enabled and the Cancel button will change to Ok. If you don't wish to wait until the search ends you can dismiss the dialog by pressing Cancel. The definition begins with an "interface" statement that specifies the target class name followed by the name(s) of its parent(s). The body of the definition can contain type, constant, attribute, method and exception declarations, followed by an implementation statement. The type declarations are preceded by the typedef keyword and are similar to the C/C++ language typedefs. The constant declarations are preceded by the const keyword and are similar to the const declarations in C/C++. The attribute declarations consist of the attribute keyword followed by the type and name of the attribute; sometimes the attribute declaration may be preceded by the readonly keyword, indicating that the attribute value can be accessed but not modified by client programs (the attribute has no "set" method). The method declarations define the signature for each method introduced by the class; the syntax is similar to the one presented in the previous chapter (the Methods page) with one addition: the parameter declarations in the parameter list are preceded by one of the following three directional attributes: in | out | inout indicating whether the parameter is to be passed from client to server (in), from server to client (out) or in both directions. The exception declarations consist of the exception keyword followed by the name of the exception and,optionally, a list of members enclosed in curly brackets; a member declaration has the following form: ; where is a valid IDL type and is an identifier. An interface definition may contain an implementation statement. The implementation statement has the following form: implementation { modifier statements }; A modifier statement gives additional implementation information about interface, attribute, method and/or type definitions. A modifier can be unqualified or qualified. A unqualified modifier is associated with the interface it is defined in and can have the following two forms: modifier; modifier = value; where can be a predefined or user-defined identifier and is an identifier, string enclosed in double quotes or a number. A qualified modifier is associated with a qualifier and can have the following two forms: qualifier : modifier; qualifier : modifier = value; where is the identifier of a IDL definition or is user defined. For more information on Interface Definition Language refer to your SOM Developer Toolkit documentation. Note: For some classes instead of the interface definition you may get the message: "No interface repository information for " This means that ObjectSpy found no entry for the specified class in the in the interface repository files specified by the SOMIR environment variable. ═══ 15. ObjectSpy SysInfo Miscellaneous Page ═══ General System Info Page. Miscellaneous information maximum path length for the currently installed file system maximum number of text, PM and DOS sessions, OS/2 boot drive, dynamic priority variation, OS/2 version number. Memory information page size, amount of physical memory in the system, amount of memory reserved for use by the operating system an device drivers, amount of swapable memory available. ═══ 16. ObjectSpy SysInfo Drives Page ═══ The Drives Page. This page displays information about the logical drives present in the system. To view the information for a specific drive, select the corresponding drive letter from the pull-down list of the Drive combination box. The following information is displayed: Location Specifies whether the drive is local or remote. Removable Specifies whether the media in the drive is removable. Values: Yes or No File System This is the type of file system that controls the device: FAT, HPFS, LAN or CDFS. This information is not available for floppy drives if no media is present. Drive Description This describes the drive type and can take one of the following values: 48 TPI LD Floppy 98 TPI HD Floppy 3.5" 720KB Floppy 3.5" 1.44MB Floppy 3.5" 4MB Floppy 8" SD Floppy 8" HD Floppy Fixed Disk Tape Drive R/W Optical Disk CD-ROM Drive Unknown Media Description This describes the media present in the drive and can take one of the following values: 3.5" 720KB diskette 3.5" 1.44MB diskette 3.5" 2.88MB diskette 3.5" diskette 5.25" SS diskette 5.25" DS diskette 8" SS,SD diskette 8" DS,SD diskette 8" DS,DD diskette Fixed Disk CD-ROM disk Unknown Media not present The next set of information corresponds to the BPB (BIOS Parameter Block) for the media currently in the drive ( A BPB is a table that describes the structure of the media). If media is not present in the drive the information displayed is the recommended BPB for the drive, based on the default media type for that drive. Bytes/Sector Sector size, in bytes. Sectors/Cluster Number of sectors per allocation unit Reserved Sectors Number of reserved sectors Number of FATs Number of File Allocation Tables Root Dir Entries Maximum number of root directory entries Total Sectors Total number of sectors in logical image (including boot sector and directories) Sectors/FAT Number of sectors occupied by a single FAT Sectors/Track Number of sectors per track Number of heads Total number of heads used to access the media Hidden Sectors Number of hidden sectors for this partition Number of Cylinders Number of cylinders for the physical device. Total Space Maximum allocable space on the media/partition. Allocated Amount of space currently allocated on the media/partition. Available Amount of space available for allocation. ═══ 17. ObjectSpy SysInfo Devices Page ═══ The Devices Page. This page displays a list of all the character and pseudocharacter devices in the system with device name, type (character or pseudocharacter) and device driver name (for pseudocharacter devices), followed by device-specific information for screen, keyboard, mouse, parallel and serial ports. The Information box contains information pertaining to the currently selected device in the Device list box. ═══ 18. ObjectSpy SysInfo Printers Page ═══ The Printers Page. The page displays the list of queues for the local machine. The Queue box below the list displays information about the currently selected queue in the list: description, default driver name, attached printers names, the priority assigned to the queue, queue status, number of jobs in the queue, active hours of the queue specified by start and end times. The Device Capabilities button opens a dialog describing the printer device for the selected queue. The Forms... button opens a dialog that presents the forms available for the selected device. The Job Properties... button will make a request to the printer driver to display its job properties dialog; job properties affect the appearance of a single print job without changing system-wide settings. Page orientation, number of copies and pages are typical items found in a job properties dialog. ═══ 19. Device Caps Dialog ═══ Device Capabilities Technology Device techology; the following is a list of possible values: Vector plotter Raster display Raster printer Raster camera PostScript device Unknown Media size Width and height of print media in pels. Resolution Horizontal and vertical resolution of the device in pels. per meter. Colors Number of distinct colors supported at the same time. Fonts Number of device-specific fonts. ═══ 20. Forms Dialog ═══ Forms Dialog The Form Information box contains information for the currently selected form in the form list: Form size Physical form size in millimeters. Attribute Indicates if the form is the current default form ("Current") or if the form may be selected ("Selectable"). If neither is true for a form, that form is not installed on the device and should no be used. Left, right, bottom, top clip Specifies the coordinates in millimeters of the printable area of the form within the physical page. ═══ 21. ObjectSpy Script File Page ═══ The Script File Page. The Script File Page provides a tool for automating repetitive class registration and instance creation operations by allowing the user to create, edit and run script files for such operations. Along with commands for class operations such as add, delete, replace, unreplace and create instance, the script files support file copy commands so that by building a script file you're actually getting a class/object installation program in no time at all and without writing one line of code. The entry field in the Script File group box contains the name of the currently selected script file (if any). The New... button allows user to create a new script file. See Create New Script. The Open... button will display a file selection dialog for script files (default .SCR extension). The user can select the script file to be opened and press Ok or abort the operation by pressing Cancel. Once a file was selected, ObjectSpy will open the file and attempt to read and display its contents in the Contents list box. The Contents list box displays the contents of the currently opened script file (if any); the following table lists the syntax for script file commands: ┌─────────────────────────┬─────────────────────────┐ │Command │Action │ ├─────────────────────────┼─────────────────────────┤ │COPY source destination │Copies the "source" file │ │ │to "destination" │ ├─────────────────────────┼─────────────────────────┤ │ADD class dll │Adds a new class to WPS │ │ │class hierarchy │ ├─────────────────────────┼─────────────────────────┤ │DELETE class │Removes a class from WPS │ │ │class hierarchy │ ├─────────────────────────┼─────────────────────────┤ │INSTANCE title class │Creates an instance of a │ │location [setup] │class │ ├─────────────────────────┼─────────────────────────┤ │REPLACE class │Replaces a class with │ │replacement_classs │another class │ ├─────────────────────────┼─────────────────────────┤ │UNREPLACE class │Unreplaces a previously │ │replacement_class │replaced class │ └─────────────────────────┴─────────────────────────┘ The Edit and Delete buttons on the right side of the Contents list box act upon the currently selected command in the list: The Edit button will bring up the input dialog box corresponding to that command, allowing user to change the command's arguments. The contents of the dialog box depend on the type of command selected. Refer to the Script Commands Input Dialogs for details. The Delete button will remove the selected command from the from the Contents list box. The Add Commands to Script box contains a group of six buttons, each corresponding to a script command; their function is to allow the user to add commands to the script file, by displaying a command-specific dialog box where the command arguments can be entered. The Save button will save the contents of the script file to the disk. The Undo button will undo any changes made to the script file since the last Save ( or Open or New, if Save was not applied). The Run button will attempt to execute the commands in the Contents list box. If a command fails, a message box containing the command and three buttons (Abort, Retry, Ignore) representing possible courses of action will be displayed: The Abort button will end the execution of the script. The Retry button will allow the user to edit the failed command by bringing up the input dialog for the command, then it will attempt to execute the command again. The Ignore button will ignore the failed command and resume script execution. See also: Script Commands Input Dialogs ═══ 22. Create New Script File Dialog ═══ Create New Script Enter the name for the new script file (if no extension is specified,.SCR is assumed) and press Ok to create the file, or abort the operation by selecting Cancel. ═══ 23. Script Commands Input Dialogs ═══ Script Commands Input Dialogs These dialogs are displayed each time user presses Edit... to change an existing script command (in which case the entry fields of the dialog contain the command arguments) or selects one of the Add Commands to Script buttons to add a new command to the script (in which case the entry fields of the dialog are empty). See: Copy File Dialog Add Class Dialog Delete Class Dialog Create Instance Dialog Replace Class Dialog Unreplace Class Dialog ═══ 24. Copy File Dialog ═══ Copy File Dialog Enter the source and destination file names in the designated entry fields, then press Ok to add/change the command; press Cancel to abort the operation. ═══ 25. Add Class Dialog ═══ Add Class Dialog Enter the new class name, and the name of the DLL that contains the class definition in the entry fields provided, then press Ok to add/change the command; press Cancel to abort the operation. ═══ 26. Delete Class Dialog ═══ Delete Class Dialog Enter the name of the class to be deleted in the entry field provided, then press Ok to add/change the command; press Cancel to abort the operation. ═══ 27. Create Instance Dialog ═══ Create Instance Dialog Enter the object title, class, location and, optionally, the setup string in the designated entry fields and press Ok to add/change the command; press Cancel to abandon the operation. ═══ 28. Replace Class Dialog ═══ Replace Class Dialog Enter the original class and replacement class names in the designated entry fields and press Ok to add/change the command; press Cancel to abandon the operation. ═══ 29. Unreplace Class Dialog ═══ Unreplace Class Dialog Enter the original class and replacement class names in the designated entry fields and press Ok to add/change the command; press Cancel to abandon the operation. ═══ 30. ObjectSpy Profile Page ═══ The Profile Files Page. Initialization (profile) files are used to store important data between instances of an application. OS/2 uses two INI files to store data and configuration information: the user profile file, OS2.INI, and the system profile file, OS2SYS.INI In addition to these two files, applications can create and access their own INI files. An INI file is like any other file. Can be renamed, copied, written to, moved or deleted. Unlike Microsoft Windows INI files, OS/2 INI files are binary and that makes them less accessible. In order to access these files you need an application specifically designed to work with them. OS/2 INI files are created and maintained using the Profile Management API and they all share the same three-tiered layout. Each INI file consists of one or more sections (applications); each section contains one or more keys; each key consists of two parts: name and data. Both the application and key name are null-terminated strings. The data associated with a key can be a null-terminated string or a block of binary data. The Profile Files Page is a INI file management tool that can be used to view and change any OS/2 INI file. The INI File box contains the current profile selection: User Profile, System Profile, User and System Profile or the full path name of a user-selected INI file (see the Options Menu). The Application Name list box contains the list of all application entries in the currently selected INI file(s), in alphabetical order; that make it easier to detect any duplicates. First time into the application this list displays the contents of both user and system INI files. The Key Name list box contains the key names for the currently selected application name. The Data window below displays the data for the currently highlighted key in both hex and ASCII text format. Each line of data displays 16 bytes preceded, in the hex section, by the offset (hex) of the beginning of the line in the data block. The Options button brings up the Options Menu . The Backup button will create a copy of the currently selected INI file(s) in the same directory and with the same name as the original and a .BAK extension. We suggest you use this feature before making any changes to an INI file, especially the system INIs. Care should be taken when changing system INI files since OS/2 relies on the information stored in those files. We suggest that you don't attempt to make any changes to OS2.INI and OS2SYS.INI unless you are familiar with the settings you are changing and their effect. ═══ 31. Profile Option Menu ═══ Options Menu The first four options allow the user to select the INI file to be displayed; the check mark indicates the currently selected option. The User Profile option will display the contents of OS2.INI file. The System Profile option will display the contents of OS2SYS.INI file. The User and System Profile option will display the contents of both OS2.INI and OS2SYS.INI files. Choosing Other... will bring up a file selection dialog for INI files allowing user to select the INI file to display. You can select an existing INI file or enter the name of a new one. The full path name of the file will appear in the INI File box. The Add New Application option will bring up the Add Section dialog box. All entry fields are empty and they all have to be filled out before the Ok button is enabled. The Add New Key option allows the user to add a new key entry to the currently highlighted application. Again the Add Section dialog is displayed, with the Application Name entry field set to the selected application name; editing is disabled for this field. The Key Name and Data fields must be filled before Ok is enabled. Choosing Delete Selected Application will remove the highlighted application and its associated keys from the INI file. Choosing Delete Selected Key will remove the highlighted key name together with its data from the INI file. The Edit Selected Key Data option allows user to edit the data for the currently selected key. A Edit Key Data dialog is displayed which is similar to the Add Section dialog, only this time all the fields are set to the selected application name, key name and key data respectively; editing is enabled only for the Data field. See Editing Key Data for details on data editing. ═══ 32. Add Section Dialog ═══ Add Section Dialog This dialog appears whenever user selects "Add New Aplication", "Add New Key", or "Edit Selected Key Data" option from the Options menu (for the last option the dialog title changes to "Edit Key Data"). For a detailed explanation of each field, select from the list below: Add New Application Add New Key Edit Selected Key Data Editing Key Data ═══ 33. Add New Application ═══ Enter the application name, key name and key data into the designated input fields and press Ok to add the new application. The new application will be added to the INI file and to the Application list box. If an existing application name was entered, no new application entry is created; rather a new key entry will be added to the application. See also: Editing Key Data ═══ 34. Add New Key ═══ The application name entry field is set to the currently selected application and editing is disabled for that field. Enter the key name and key data into the designated input fields and press Ok to add the new key. The new key will be added to the selected application. If an existing key name was entered, no new key entry is created and the new key data will replace the existing data for that key. See also: Editing Key Data ═══ 35. Edit Selected Key Data ═══ The Application Name, Key Name and Data entry fields are set to the selected application, key name and key data; editing is disabled for application and key name. Edit the key data and press Ok; the new data value will replace the existing one in the INI file and Data window on the Profile Page. See also: Editing Key Data ═══ 36. Editing Key Data ═══ The Data entry field in the Add Section dialog box is a multiline edit control supplied with a vertical scroll bar; the entered text wraps at the end of line so the user is not forced to enter unneeded sequences for visibility purposes. The field was mainly intended for ASCII text input but you can enter binary data too. To enter a binary data byte, enter a pound sign (#) followed by two hex digits for the value (example: #0A will be converted and stored in the data block as a byte with the hex value 0A). That enables the user to mix text and binary values when entering the data. The following example represents the input for a line of text terminated by : This is a line of text#0D#0A The following conventions apply: 1. To enter a pound sign character, double it: ##. 2. If no binary data has been entered (there are no #hh sequences), the data is assumed to be ASCII text and a null terminator will be appended. 3. If the input field contains binary data specifiers (#hh sequences) the data is assumed to be binary and no null terminator will be appended. So if your data contains null-terminated text you have to enter the null terminator as #00. Example: This is a text item in a binary data block#00 4. Pressing Enter while editing the data field will place the input cursor at the beginning of the next line and insert a #0D#0A sequence in the data block. 5. Both uppercase and lowercase hex digits are supported 6. When this dialog is used to edit existing key data the data is loaded into the entry field using the convention described above for binary data representation and the value is assumed to be binary so that a null terminated ASCII text will appear like: ASCII text#00 ═══ 37. Object Setup Keynames ═══ Predefined Keynames and Values This section contains a description of the setup strings defined by the Workplace Shell classes. The following is a list of the WPS that currently define setup strings: WPObject WPDisk WPFolder WPLaunchPad WPPalette WPColorPalette WPFontPalette WPSchemePalette WPPrinter WPRPrinter WPProgram WPProgramFile WPShadow ═══ 38. WPObject Setup Strings ═══ Setup Strings Defined by WPObject ┌───────────────────────────────────────────────────────────────────────────────────────┐ │Key Name/Description Value Meaning │ ├───────────────────────────────────────────────────────────────────────────────────────┤ │CCVIEW DEFAULT The default system value is used │ │Specifies the │ │concurrent view YES New views of the object are created │ │setting used when every time the user selects Open │ │the user selects Open │ │Open NO The existing view of the object (if any) │ │ is resurfaced when the user selects Open. │ ├───────────────────────────────────────────────────────────────────────────────────────┤ │DEFAULTVIEW SETTINGS Sets the default open view to the Settings │ │Sets the default view │ │open view. │ │ id Sets the default open view to the id of a │ │ user defined view. │ │ │ │ DEFAULT Sets the default open view to the │ │ object's class default view (default) │ ├───────────────────────────────────────────────────────────────────────────────────────┤ │HELPLIBRARY filename Name of the help library file. │ │Sets the help library │ ├───────────────────────────────────────────────────────────────────────────────────────┤ │HELPPANEL id Id of the default help panel │ │Sets the object's │ │default help. │ ├───────────────────────────────────────────────────────────────────────────────────────┤ │HIDEBUTTON YES Views of the object have a hide button │ │ as opposed to a minimize button (default) │ │ │ │ NO Views of the object have a minimize button │ │ as opposed to a hide button │ ├───────────────────────────────────────────────────────────────────────────────────────┤ │ICONFILE filename Icon file name │ │Sets the object's │ │icon │ ├───────────────────────────────────────────────────────────────────────────────────────┤ │ICONPOS x,y The icon position in the object's folder in │ │Sets the object's percentage coordinates │ │initial icon position │ ├───────────────────────────────────────────────────────────────────────────────────────┤ │ICONRESOURCE id,module The resource id of the icon and the module │ │Sets the object's file name where the resource is located. │ │icon to a resource │ │from a dynamic link │ │module │ ├───────────────────────────────────────────────────────────────────────────────────────┤ │MINWIN HIDE Hide the view if the minimize button is │ │Sets the object's selected │ │minimized view │ │ VIEWER Minimize the view to the minimized window │ │ viewer │ │ │ │ DESKTOP Minimize to the Desktop │ ├───────────────────────────────────────────────────────────────────────────────────────┤ │NOCOPY YES The object cannot be copied; there is no │ │Sets the object's Copy option in the object's context menu. │ │no copy property. │ │ NO The object can be copied │ ├───────────────────────────────────────────────────────────────────────────────────────┤ │NODELETE YES The object cannot be deleted; the object │ │Sets the object's cannot be dragged to the shredder and there │ │no delete property. is no Delete option in the object's context │ │ menu. │ │ │ │ NO The object can be deleted │ ├───────────────────────────────────────────────────────────────────────────────────────┤ │NODRAG YES The object cannot be moved, copied or dragged│ │Sets the object's there are no Copy, Move or Pickup options │ │no drag property. in the object's context menu. │ │ │ │ NO The object can be dragged │ ├───────────────────────────────────────────────────────────────────────────────────────┤ │NODROP YES No object can be dropped on this object. │ │Sets the object's │ │no drop property. NO The object allows other objects to be │ │ dropped on it. │ ├───────────────────────────────────────────────────────────────────────────────────────┤ │NOLINK YES The object cannot have shadows; there │ │Sets the object's is no Create Shadows option in the object's │ │no link property context menu. │ │ │ │ NO The object can have shadows (default) │ ├───────────────────────────────────────────────────────────────────────────────────────┤ │NOMOVE YES The object cannot be moved; there is no │ │Sets the object's Move option in the object's context menu. │ │no move property │ │ NO The object can be moved │ ├───────────────────────────────────────────────────────────────────────────────────────┤ │NOPRINT YES The object cannot be printed; there is no │ │Sets the object's Print option in the object's context menu │ │no print property. and the object cannot be dragged onto a │ │ Printer object. │ │ │ │ NO The object can be printed. │ ├───────────────────────────────────────────────────────────────────────────────────────┤ │NORENAME YES The object cannot be renamed; its title │ │Sets the object's cannot be changed either by editing the │ │no rename property. string below the icon or by changing it │ │ on the General page of the Settings notebook.│ │ │ │ NO The object can be renamed. │ ├───────────────────────────────────────────────────────────────────────────────────────┤ │NOSETTINGS YES The object cannot be opened in settings view;│ │Sets the object's there is no Settings option in the object's │ │no settings property. context menu. │ │ │ │ NO The object can be opened in Settings view. │ ├───────────────────────────────────────────────────────────────────────────────────────┤ │NOSHADOW YES The object cannot have shadows; there │ │Sets the object's is no Create Shadows option in the object's │ │no link property context menu. │ │ │ │ NO The object can have shadows │ ├───────────────────────────────────────────────────────────────────────────────────────┤ │NOTVISIBLE YES The object is invisible. │ │Sets the object's │ │not visible property. NO The object is visible. │ ├───────────────────────────────────────────────────────────────────────────────────────┤ │OBJECTID The object's id: an unique string preceded by│ │Sets the object's id. a "<" and terminated with a ">". │ ├───────────────────────────────────────────────────────────────────────────────────────┤ │OPEN SETTINGS Opens the settings view. │ │Sets the view to be │ │opened when the object DEFAULT Opens the default view. │ │is created or when │ │WinSetObjectData is calle │ ├───────────────────────────────────────────────────────────────────────────────────────┤ │TEMPLATE YES The object is a template. │ │Sets the object's │ │template property. NO The object is not a template │ ├───────────────────────────────────────────────────────────────────────────────────────┤ │TITLE title The object's title. │ │Sets the object title. │ └───────────────────────────────────────────────────────────────────────────────────────┘ ═══ 39. WPPalette Setup Strings ═══ Setup Strings Defined by WPPalette ┌───────────────────────────────────────────────────────────────────────────────────────┐ │Key Name/Description Value Meaning │ ├───────────────────────────────────────────────────────────────────────────────────────┤ │XCELLCOUNT columns Number of columns of cells (default │ ├───────────────────────────────────────────────────────────────────────────────────────┤ │YCELLCOUNT rows Number of rows of cells (default │ ├───────────────────────────────────────────────────────────────────────────────────────┤ │XCELLWIDTH width Cell width in dialog units │ ├───────────────────────────────────────────────────────────────────────────────────────┤ │YCELLHEIGHT height Cell height in dialog units │ ├───────────────────────────────────────────────────────────────────────────────────────┤ │XCELLGAP gap Horizontal distance between cells in dialog │ │ units │ ├───────────────────────────────────────────────────────────────────────────────────────┤ │YCELLGAP gap Vertical distance between cells in dialog │ │ units │ └───────────────────────────────────────────────────────────────────────────────────────┘ ═══ 40. WPColorPalette Setup Strings ═══ Setup Strings Defined by WPColorPalette ┌───────────────────────────────────────────────────────────────────────────────────────┐ │Key Name/Description Value Meaning │ ├───────────────────────────────────────────────────────────────────────────────────────┤ │COLORS color_list List of RGB color values separated by commas.│ │Sets the color Each value is a six-digit hex value in the │ │values for each cell format 0xRRGGBB where RR,GG,BB are the red, │ │ green and blue values ranging between 0x00 │ │ and 0xFF. │ ├───────────────────────────────────────────────────────────────────────────────────────┤ │XCELLCOUNT columns Number of columns of cells (default │ ├───────────────────────────────────────────────────────────────────────────────────────┤ │YCELLCOUNT rows Number of rows of cells (default │ └───────────────────────────────────────────────────────────────────────────────────────┘ ═══ 41. WPFontPalette Setup Strings ═══ Setup Strings Defined by WPFontPalette ┌───────────────────────────────────────────────────────────────────────────────────────┐ │Key Name/Description Value Meaning │ ├───────────────────────────────────────────────────────────────────────────────────────┤ │FONTS font_list List of font specifiers separated by commas. │ │Sets the fonts Each font specifier has the format: │ │for each cell size.facename │ │ Example: │ │ FONTS=8.Helvetica,10.Helvetica,12.Helvetica, │ │ 10.Courier,12.Courier,10.System │ ├───────────────────────────────────────────────────────────────────────────────────────┤ │XCELLCOUNT columns Number of columns of cells (default │ ├───────────────────────────────────────────────────────────────────────────────────────┤ │YCELLCOUNT rows Number of rows of cells (default │ └───────────────────────────────────────────────────────────────────────────────────────┘ ═══ 42. WPSchemePalette Setup Strings ═══ Setup Strings Defined by WPSchemePalette ┌───────────────────────────────────────────────────────────────────────────────────────┐ │Key Name/Description Value Meaning │ ├───────────────────────────────────────────────────────────────────────────────────────┤ │YES Set the palette │ │ system palette │ │ │ │NO Does not set th │ │ original system │ ├───────────────────────────────────────────────────────────────────────────────────────┤ │SCHEMES scheme_list List of separated by commas. │ │Sets the fonts Each font specifier has the format: │ │for each cell size.facename │ │ Example: │ │ FONTS=8.Helvetica,10.Helvetica,12.Helvetica, │ │ 10.Courier,12.Courier,10.System │ ├───────────────────────────────────────────────────────────────────────────────────────┤ │XCELLCOUNT columns Number of columns of cells (default │ ├───────────────────────────────────────────────────────────────────────────────────────┤ │YCELLCOUNT rows Number of rows of cells (default │ └───────────────────────────────────────────────────────────────────────────────────────┘ ═══ 43. WPDisk Setup Strings ═══ Setup Strings Defined by WPDisk ┌───────────────────────────────────────────────────────────────────────────────────────┐ │Key Name/Description Value Meaning │ ├───────────────────────────────────────────────────────────────────────────────────────┤ │DRIVENUM drive_num logical drive number (1-26) │ │Sets the logical │ │drive │ └───────────────────────────────────────────────────────────────────────────────────────┘ ═══ 44. WPFolder Setup Strings ═══ Setup Strings Defined by WPFolder ┌───────────────────────────────────────────────────────────────────────────────────────┐ │Key Name/Description Value Meaning │ ├───────────────────────────────────────────────────────────────────────────────────────┤ │ALWAYSSORT YES Sort order is always maintained │ │ │ │ NO Sort order is not maintained (default) │ ├───────────────────────────────────────────────────────────────────────────────────────┤ │BACKGROUND im_file, im_file - full path name of the image file │ │ im_mode, scale, im_mode - image mode: │ │Sets the folder bk_type, N = normal │ │background bk_color T = tiled │ │ S = scaled │ │ scale - scaling factor │ │ bk_type - background type: │ │ I = image │ │ C = color │ │ bk_color - background color: 3 numbers │ │ representing the RGB values │ │ of the background color │ │ │ │ Examples: │ │ BACKGROUND=c:\bmp\sample.bmp,S,4,I │ │ BACKGROUND=(none),,,C,0 128 128 │ ├───────────────────────────────────────────────────────────────────────────────────────┤ │DEFAULTVIEW ICON The default open view is the icon view │ │Sets the default open TREE The default open view is the tree view │ │view for the folder DETAILS The default open view is the details view │ ├───────────────────────────────────────────────────────────────────────────────────────┤ │DETAILSCLASS classname Name of the class that defines the details │ │Sets the class for data in details view │ │which the details │ │are displayed │ │in the folder's │ │detail view. │ ├───────────────────────────────────────────────────────────────────────────────────────┤ │DETAILSFONT size.facename Size and facename of the font. │ │Sets the font used for │ │details view Example: DETAILSFONT=10.Helv │ ├───────────────────────────────────────────────────────────────────────────────────────┤ │DETAILSVIEW NORMAL Normal size icons are displayed. │ │Sets the details view │ │icon size. MINI Smaller size icons are displayed (default). │ ├───────────────────────────────────────────────────────────────────────────────────────┤ │ICONFONT size.facename Size and facename of the font. │ │Sets the font used │ │for icon view │ ├───────────────────────────────────────────────────────────────────────────────────────┤ │ICONNFILE 1,filename filename = filename of the open file icon │ │Sets the open folder │ │icon Example: ICONNFILE=1,C:\ICONS\OPF.ICO │ ├───────────────────────────────────────────────────────────────────────────────────────┤ │ICONNRESOURCE 1,resid,module resid = icon resource id │ │Sets the open folder module = name of the module where the │ │icon to a resource resource is located │ │from a module. Example: │ │ ICONNRESOURCE=1,101,C:\ICONS\ICONS.DLL │ ├───────────────────────────────────────────────────────────────────────────────────────┤ │ICONVIEW FLOWED Arrange icons in columns across the screen │ │Sets the icon view or │ │style (format and/or NONFLOWED Arrange icons in a column from the top │ │icon size). or to the bottom of the screen │ │ NONGRID Icons are displayed without columns │ │ │ │ NORMAL Normal size icons are displayed │ │ or │ │ MINI Smaller size icons are displayed │ │ or │ │ INVISIBLE No icons are displayed │ │ │ │ Default: NOGRID,NORMAL │ ├───────────────────────────────────────────────────────────────────────────────────────┤ │ICONVIEWPOS x,y,cx,cy position and size in percentages of screen │ │Sets the initial size (0-100) │ │icon view position │ │and size on the screen │ ├───────────────────────────────────────────────────────────────────────────────────────┤ │OPEN ICON Opens the icon view │ │Sets the view to be TREE Opens the tree view │ │opened when the folder DETAILS Opens the details view │ │is created or when │ │WinSetObjectData is │ │called │ ├───────────────────────────────────────────────────────────────────────────────────────┤ │REMOVEFONTS YES Removes all instance fonts from the │ │ folder. │ │ NO Does not remove instance fonts from the │ │ folder (default) │ ├───────────────────────────────────────────────────────────────────────────────────────┤ │SORTBYATTR offset_list List of offsets of the sort fields │ │Sets the attributes in the sort class, separated by commas │ │to sort by. Example: │ │ SORTBYATTR=0,1,3 │ ├───────────────────────────────────────────────────────────────────────────────────────┤ │SORTCLASS classname Name of the class that provides the │ │Sets the class sort criteria. │ │object to sort by. Default: WPFileSystem │ ├───────────────────────────────────────────────────────────────────────────────────────┤ │TREEFONT size.facename Font size and facename. │ │Sets the font used │ │for tree view │ ├───────────────────────────────────────────────────────────────────────────────────────┤ │TREEVIEW LINES The tree structure is displayed with │ │Sets the tree view or connecting lines (default) │ │style (format and/or NOLINES The tree structure is displayed without │ │icon size) connecting lines │ │ │ │ NORMAL Normal size icons are displayed │ │ or │ │ MINI Smaller size icons are displayed │ │ or │ │ INVISIBLE No icons are displayed │ │ │ │ Default: LINES,NORMAL │ ├───────────────────────────────────────────────────────────────────────────────────────┤ │WORKAREA YES The folder is a workarea │ │Specifies whether the NO The folder is not a workarea │ │folder is a work area. │ └───────────────────────────────────────────────────────────────────────────────────────┘ ═══ 45. WPLaunchPad Setup Strings ═══ Setup Strings Defined by WPLaunchPad ┌───────────────────────────────────────────────────────────────────────────────────────┐ │Key Name/Description Value Meaning │ ├───────────────────────────────────────────────────────────────────────────────────────┤ │FPOBJECTS IDs (or list of object ids and/or filenames separated│ │Adds objects to the filenames) by commas │ │end of the LaunchPad │ ├───────────────────────────────────────────────────────────────────────────────────────┤ │DRAWEROBJECTS drawer, drawer = drawer number │ │Adds objects to the end object_list object_list = list of object ids and/or │ │of the indicated drawer filenames, separated by commas │ ├───────────────────────────────────────────────────────────────────────────────────────┤ │LPCLOSEDRAWER YES Drawer is closed │ │Specifies whether the NO Drawer stays open │ │LaunchPad drawers will │ │close after an object │ │in the drawer is opened │ ├───────────────────────────────────────────────────────────────────────────────────────┤ │LPACTIONSTYLE TEXT Displays the action buttons as text (default)│ │Sets the action buttons OFF Turns off the display of action buttons │ │style MINI Displays the action buttons as mini-icons │ │ NORMAL Displays the action buttons as normal icons │ ├───────────────────────────────────────────────────────────────────────────────────────┤ │LPVERTICAL YES The Launch Pad will be displayed verticaly │ │Sets the appearance NO The Launch Pad will be displayed horizontaly │ │of the Launch Pad (default) │ ├───────────────────────────────────────────────────────────────────────────────────────┤ │LPTEXT YES The object titles will appear on the │ │Specifies whether the Launch Pad │ │object titles will be NO The object titles will be hidden │ │displayed on the Launch P │ ├───────────────────────────────────────────────────────────────────────────────────────┤ │LPTEXT YES The titles will appear on the objects │ │Specifies whether the in the drawers │ │object titles will be NO The object titles will be hidden │ │displayed for the │ │objects in the drawers │ ├───────────────────────────────────────────────────────────────────────────────────────┤ │LPSMALLICONS YES Objects are displayed using small icons │ │Sets the object icons NO Objects are displayed using normal icons │ │style │ ├───────────────────────────────────────────────────────────────────────────────────────┤ │LPHIDECTL YES The frame controls are hidden │ │Sets the state of NO The frame controls are displayed │ │the frame controls │ │(title bar and system men │ ├───────────────────────────────────────────────────────────────────────────────────────┤ │LPFLOAT YES The Launch Pad will float on top of │ │ all other windows │ │ NO The Launch Pad will not float on top │ │ of other windows │ └───────────────────────────────────────────────────────────────────────────────────────┘ ═══ 46. WPPrinter Setup Strings ═══ Setup Strings Defined by WPPrinter ┌───────────────────────────────────────────────────────────────────────────────────────┐ │Key Name/Description Value Meaning │ ├───────────────────────────────────────────────────────────────────────────────────────┤ │APPDEFAULT YES The printer is the default printer object │ │Specifies whether this NO The printer is not the default printer │ │printer is to become object │ │the application's │ │default printer object │ ├───────────────────────────────────────────────────────────────────────────────────────┤ │DEFAULTVIEW DETAILS The default open view is the details view │ │Sets the default open ICON The default open view is the icon view. │ │view for this printer │ │object │ ├───────────────────────────────────────────────────────────────────────────────────────┤ │JOBDIALOGBEFOREPRINT YES Display the job properties dialog │ │Specifies whether the before printing │ │job properties dialog NO Do not display the job properties dialog │ │is to be displayed before printing │ │before printing │ ├───────────────────────────────────────────────────────────────────────────────────────┤ │JOBPROPERTIES filename Full path name of a binary file │ │Specifies the containing the default job properties │ │job properties file for the printer object. │ │for this printer │ ├───────────────────────────────────────────────────────────────────────────────────────┤ │OUTPUTTOFILE YES The output goes to a file; the user will │ │Specifies whether be prompted for a file name before printing │ │the output from NO The output goes to the printer device. │ │this printer should │ │go to a file. │ ├───────────────────────────────────────────────────────────────────────────────────────┤ │PORTNAME port_list List of installed port names, separated by │ │Sets the port(s) commas. │ │to which this printer │ │object is to be attached │ ├───────────────────────────────────────────────────────────────────────────────────────┤ │PRINTDRIVER driver_list A list of complete printer driver names in │ │Specifies the printer the form: │ │driver(s) for this printe driver.device │ │ separated by commas │ ├───────────────────────────────────────────────────────────────────────────────────────┤ │PRINTERSPECIFICFORMAT YES The printer object spools print jobs in │ │ PM_Q_RAW format │ │ NO The printer object spools print jobs in │ │ PM_Q_STANDARD format │ ├───────────────────────────────────────────────────────────────────────────────────────┤ │QSTARTTIME time The time when the printer object starts │ │ printing, in the format: │ │ HH:MM │ │ based on a 24-hour clock. │ ├───────────────────────────────────────────────────────────────────────────────────────┤ │QSTOPTIME time The time when the printer object stops │ │ printing, in the format: │ │ HH:MM │ │ based on a 24-hour clock. │ ├───────────────────────────────────────────────────────────────────────────────────────┤ │QUEUENAME name The local queue name for the printer object │ ├───────────────────────────────────────────────────────────────────────────────────────┤ │QUEUEDRIVER qdrvname The queue driver name │ ├───────────────────────────────────────────────────────────────────────────────────────┤ │SEPARATORFILE filename Name of the separator file that prints before│ │ each print job │ └───────────────────────────────────────────────────────────────────────────────────────┘ ═══ 47. WPRPrinter Setup Strings ═══ Setup Strings Defined by WPRPrinter ┌───────────────────────────────────────────────────────────────────────────────────────┐ │Key Name/Description Value Meaning │ ├───────────────────────────────────────────────────────────────────────────────────────┤ │ICON filename The name of the .ICO file to be used as the │ │ icon for this object │ ├───────────────────────────────────────────────────────────────────────────────────────┤ │NETID netid The name of the printer resource as it is │ │ known to the network │ ├───────────────────────────────────────────────────────────────────────────────────────┤ │REFRESHINTERVAL value Time interval, in seconds, when the printer │ │ is refreshed │ ├───────────────────────────────────────────────────────────────────────────────────────┤ │SHOWJOBS ALL All jobs are displayed │ │Specifies which jobs OWN Only the current user's jobs are displayed │ │are displayed for │ │this printer object │ └───────────────────────────────────────────────────────────────────────────────────────┘ ═══ 48. WPProgram Setup Strings ═══ Setup Strings Defined by WPProgram and WPProgramFile ┌───────────────────────────────────────────────────────────────────────────────────────────────────┐ │Key Name/Description Value Meaning │ ├───────────────────────────────────────────────────────────────────────────────────────────────────┤ │ASSOCFILTER filter_list List of filename filters, separated by │ │Sets the filename commas. │ │filter(s) for files │ │associated with this Example: │ │program ASSOCFILTER=*.DOC,*.TXT; │ ├───────────────────────────────────────────────────────────────────────────────────────────────────┤ │ASSOCTYPE type_list One or more strings designating file types, │ │Sets the file type(s) separated by commas. │ │associated with this The following are predefined file types: │ │program Plain Text │ │ OS/2 Command File │ │ DOS Command File │ │ Executable │ │ Metafile │ │ Bitmap │ │ Icon │ │ Binary Data │ │ Dynamic Link Library │ │ C Code │ │ Pascal Code │ │ BASIC Code │ │ COBOL Code │ │ FORTRAN Code │ │ Assembler Code │ │ Library │ │ Resource File │ │ Object Code │ │ │ │ Example: │ │ ASSOCTYPE=Binary Data,Icon │ ├───────────────────────────────────────────────────────────────────────────────────────────────────┤ │EXENAME filename Sets the name of the program │ ├───────────────────────────────────────────────────────────────────────────────────────────────────┤ │MAXIMIZED YES The program window is maximized at startup │ │Specifies whether NO The program window is set to normal upon │ │the program window startup (default). │ │is to be maximized │ │at startup │ ├───────────────────────────────────────────────────────────────────────────────────────────────────┤ │MINIMIZED YES The program window is minimized at startup │ │Specifies whether NO The program window is set to normal upon │ │the program window startup (default). │ │is to be maximized │ │upon startup │ ├───────────────────────────────────────────────────────────────────────────────────────────────────┤ │PROGTYPE FULLSCREEN Full-screen mode │ │Sets the session type PM PM session │ │ PROG_30_STD Standard compatibility │ │ full-screen mode │ │ PROG_31_ENH Enhanced compatibility │ │ full-screen mode │ │ PROG_31_ENHSEAMLESSCOMMON WIN-OS/2 window in the WIN-OS/2 │ │ enhanced compatibility common session │ │ PROG_31_ENHSEAMLESSVDM WIN-OS/2 window in a separate session │ │ enhanced compatibility mode │ │ PROG_31_STD Standard compatibility │ │ full-screen mode │ │ PROG_31_STDSEAMLESSCOMMON WIN-OS/2 window in the WIN-OS/2 │ │ standard compatibility common session │ │ PROG_31_STDSEAMLESSVDM WIN-OS/2 window in a separate session │ │ standard compatibility mode │ │ SEPARATEWIN WIN-OS/2 window running in a │ │ separate VDM │ │ VDM DOS full-screen │ │ WIN WIN_OS/2 full-screen │ │ WINDOWABLEVIO OS/2 windowed │ │ WINDOWEDVDM DOS windowed │ │ WINDOWEDWIN WIN-OS/2 window │ ├───────────────────────────────────────────────────────────────────────────────────────────────────┤ │NOAUTOCLOSE YES Leaves the window opened when the program │ │ terminates │ │ NO Closes the window when the program │ │ terminates (default) │ ├───────────────────────────────────────────────────────────────────────────────────────────────────┤ │PARAMETERS param_list Sets the parameters list; may include │ │ substitution characters. │ ├───────────────────────────────────────────────────────────────────────────────────────────────────┤ │SET envar=value envar = environment variable │ │Sets the program value = the value of the environment variable│ │environment │ │ Example: │ │ SET PATH=C │ ├───────────────────────────────────────────────────────────────────────────────────────────────────┤ │STARTUPDIR pathname Sets the working directory │ └───────────────────────────────────────────────────────────────────────────────────────────────────┘ ═══ 49. WPShadow Setup Strings ═══ Setup Strings Defined by WPShadow ┌───────────────────────────────────────────────────────────────────────────────────────┐ │Key Name/Description Value Meaning │ ├───────────────────────────────────────────────────────────────────────────────────────┤ │SHADOWID (or Object id of fully qualified pathname of the │ │Specifies the object filename) source object. │ │for which this object │ │is a shadow │ └───────────────────────────────────────────────────────────────────────────────────────┘