Chapter 1

mpfile Specifies the location of the multibitmap file. Here we use a special case of
"*", which is described in more detail below.
bmpid The enum for the relevant bitmap, defined in the generated .mbg file.
bmpmask The enum for the corresponding bitmap mask, also defined in the .mbg
file.
The asterisk used for each bmpfile argument is shorthand (in these circumstances only)
for 'my own .mbm file'. For this to work, your .mbm file must have the same name as your
.app file and be installed in the same folder. This works for us because we deliberately
constructed our.mbm to follow these conventions by calling it Hellogui.mbm in the project
specification file, HelloGui.mmp. Under the emulator, the icon is always placed in the same
folder as our .app file but, as we shall see later, you must be careful to install it in the right
place on the target phone.
It's possible to specify other .mbm files within the bmpfile statement as well, but you have
to supply the full file path in order to do so. Some potentially useful ones are the UIQ's own
System MBMs – such as qikon.mbm, quartz.mbm and eikon.mbm. These files are
located in Z:\System\Data and their corresponding .mbg files are in \epoc32\include.
These bitmaps include icons for arrowheads
used on scrollbars, bold/italic/underline symbols, various other arrows, application icons,
background textures, and more.
14.1.4 Building the Application
After making all the necessary changes to the resource file, you can finally rebuild the
HelloGUI application using the – by now familiar – bldmake and abld commands.
From a command prompt, move to the \scmp\HelloGUIfull\Groupdirectory and type:
abld reallyclean
to remove any files that might have already been built from the previous version of
HelloGUI. Then, type:
bldmake bldfiles
to create new build files incorporating the new bitmap build and resource information. Finally,
use the abld command to rebuild the full application to be tested in the emulator, in Figure
14.4.