From v8.1b onwards, the emulator can be configured to support multiple configurations, where each configuration refers to a separate fascia and screen orientation.
To support multiple configurations, each configuration needs to be
defined in its own .ini
file. The name of each of these
.ini
files is then placed into epoc.ini
using the
configuration
keyword.
The easiest way to see how to define multiple configurations is to compare a single configuration definition with a multiple configuration definition.
For a single configuration, all keywords and values are defined
within the epoc.ini
file; for example:
ScreenWidth 208
ScreenHeight 240
ScreenOffsetX 48
ScreenOffsetY 50
LedSize 0
fasciabitmap c1.bmp
digitizeroffsetx 0
digitizeroffsety 0
digitizerheight 100
digitizerwidth 200
colordepth color16
disabledigitizer false
ledarrangevertically
ledgap 30
ledsize 25
megabytesoffreememory 4
physicalscreenheight 4000
physicalscreenwidth 6000
pointertype pen
virtualkey EStdKeyuparrow rect 119,317 42,25
virtualkey EStdKeydownarrow rect 122,405 42,25
virtualkey EStdKeyrightarrow rect 198,362 42,25
virtualkey Estdkeyleftarrow rect 48,362 42,25
virtualkey Estdkeyenter rect 121,362 42,25
NoVersionInfo
windowtitle Single Configuration
keymap leftalt 1 estdkeydevice0
In a multiple configuration definition, each configuration is defined
in its own .ini
file instead of in epoc.ini
; the
names of these files are defined in epoc.ini
, and identified by
the configuration
keyword. For a situation where there are four
separate configurations (fro example), you replace the content of your
epoc.ini
file with:
configuration c1.ini
configuration c2.ini
configuration c3.ini
configuration c4.ini
You now need to define each of the configuration files. In this
example, we have the four files: c1.ini
, c2.ini
,
c3.ini
and c4.ini
. There are two additional keywords
that can be used when defining confguration files: OnActivation
and EmulatorControl
.
OnActivation
defines the orientation of the new fascia, and the key to be sent to the window
server when this configuration is activated.
EmulatorControl defines the action that the emulator is to take when a specific region of the screen is clicked.
|