May 20 revision

~~Struck out~~ =removed Underlined = added

Basic Bitmaps 2^nd paragraph modified:

It is worthwhile noting that 6 patterns are duplicated: patterns 3 through 8 are similar to ~~can be found again as~~ 22 (12+10), 26, 29, 34, 41, and 44. They are however independent of those bitmaps, being apparently “hard coded”

Table modified followed by a new paragraph:

Brush Pattern	Bitmap#
02	1
03	12*
04	16*
05	19*
06	24*
07	31*
08	34*
12	2
13	3
from 2 to 71 brush pattern = bitmap# + 10

* similar to this bitmap in the original DLL

The bitmaps must be defined as MONOCHROME (or 2-bit color) and not many programs give that choice. If another format may be accepted “by” the DLL, the result may be a monochrome pattern (with the color used to fill in the bitmap) that cannot accept a background color (it disappears entirely) and remains black whatever the color assigned to the foreground

Creating new bitmaps new paragraph at the end:

One requirement remains paramount: each time a pattern has been modified, or once a new one has been created, it must be saved in a monochrome bmp format. If the edit program does not offer that possibility (and Tile Studio version 1.3 does not), another program is required. It could as simple as Microsoft Paint that comes with Windows because it is just a question to open the bitmap and save it in the appropriate format.

Modifying the existing pattern palette new paragraph at the end:

Another constraining consideration is of importance if an application (meaning a WOR) is going to be open on an other installation: the modified version of the DLL must also be present on that installation. That means the risk of having version conflicts (each MI version has its MIRES version) and troubles with the network administrator as the dll is part of the “central” installation.

Constraints on the bitmaps 1^st paragraph modified

The second batch of limitations comes from the basic bitmaps themselves. First their number is exactly 61~~, for the 67 pattern ids available~~. New patterns mean loosing old ones, except for the 6 that have been identified as having “hard coded” equivalents (12, 16, 19, 24, 31,34)