Classification: |
General |
Category: |
Development |
Created: |
01/20/98 |
Modified: |
06/07/2001 |
Number: |
FAQ-0066 |
Platform: |
ER5 |
|
Question: I don't care about matching the screen size on the target platform, I just want to be able to see more of my OPL source code:
how can I make that window bigger?
Answer: The WINS emulator reads \Epoc32\Data\SYSTEM.INI to look for overrides to the default settings of various parameters [[ this
is implemented in E32\KPWINS\KP_GUI.CPP ]]. The current defaults could be achieved explicitly by using
ScreenWidth 640 ScreenHeight 240 ScreenOffsetX 123 ScreenOffsetY 53 FasciaBitmap \Epoc32\Data\Fascia.bmp CaseBitmap \Epoc32\Data\Case.bmp LedSize 14 LedOffsetX 60 LedOffsetY 45 LedGap 5 LedArrangeVertically # alternatively, LedArrangeHorizontally DebugMask 0 # for User::SetDebugMask() MegabytesOfFreeMemory 0 # use 3 for a 4 Meg machine, or 7 for an 8 Meg machine) The screen size and position are the position of the emulated LCD within the Fascia bitmap and the fascia bitmap defines
the size of the digitiser: the overall window size is big enough for both. If you change any of this, it's probably a good
idea to use an app like Paint to produce a new Fascia bitmap which contains the active "buttons" of the original in the new
places relative to the changed screen size.
The "MegabytesOfFreeMemory" setting turns on a mechanism which limits the overall memory allocation, matching more closely
the behaviour of the real machine. The default value of 0 means "no limit", and can result in the amount of Free memory being
reported as a negative value! Further Answer The suitable values for MegabytesOfFreeMemory 0, 3, and 7. I tried 1 to get a 2Mb rom and this did not work. I got OOM on
boot up.
Try other values at you peril.
Further Answer
You can now also supply the following parameters to \Epoc32\Data\SYSTEM.INI:
PhysicalScreenWidth 7620 # values are in twips, PhysicalScreenHeight 2858 # (1 twip = 1/1440th of an inch)
|