18.3 How Icons and Bitmaps are Associated on Process Menus
When a MENU style process is compiled, a standard method is used to decide what icons and/or bitmaps should be associated with itself and any object it references (i.e. the associated RDML functions, menu commands, attached process or functions, etc.,).
The association method (which is performed and locked in at compile time) works like this:
1. The "object" name (process or function) is converted into the standard name format. Usually this is identical to the object name unless it contains special characters or is too long. The method used for this conversion process is described in earlier sections of this guide.
2. A check is made in the current partitions SOURCE directory (i.e. <drive>:\X_LANSA\X_ppp\SOURCE) for a file with the same name as the object, suffixed by .ICO (icon) or .BMP (bitmap).
3. If such a file exists, the association is complete and none of the following steps are used
If step 2 does not find an association, a more complex step is invoked. This step uses a file called X_ICOBMP.DAT that may exist in the current partitions SOURCE directory (i.e. <drive>:\X_LANSA\X_ppp\SOURCE). This file is called the icon and bitmap defaulting file.
The contents of file X_ICOBMP.DAT are used to try to produce an "intelligent" default icon or bitmap association. This is done by comparing data in X_ICOBMP.DAT with name and textual information associated with the current object.
The exact layout and use of X_ICOBMP.DAT is described in detail in a following section.
If step 3 does not find an association, a "final defaulting" step is used. This produces final defaults according to this table:
| Menu Object | Default Icon And/Or Bitmap Used |
|
Process |
X_DFTPRO.ICO X_DFTPRO.BMP |
|
Function |
X_DFTFUN.ICO |
|
Menu Command |
X_DFTCMD.ICO |
|
Help |
X_DFTHLP.ICO |
|
Return to ... |
X_DFTRET.ICO |
|
Exit |
X_DFTEXT.ICO |
|
all others |
X_DFTMIS.ICO |