otherwise it wasn't actually doing anything with it. palette loading
was done as part of bitmap loading only, but this allows a specific
palette to be set which may make it easier to notice bitmap palette
mismatches in some scenarios
- medit.dtf is assumed to always be beside mapedit.exe
- assets listed in the desc file being loaded are all assumed to be
beside that same desc file
paths for both the mapedit.exe and desc file are discovered
automatically from the command line arguments received.
this, in my opinion, represents the most intuitive/logical behaviour.
before this change, you would have needed to have copied mapedit.exe
and medit.dtf to the same directory as your map desc file and all the
assets being loaded. kind of icky in my opinion.
the map_edit source on the book's cd included a prebuilt version of
the old watcom version of ack3d (with headers) which defined UINT to be
'unsigned short' while our version of ack3d defines UINT to be
'unsigned int'
the map_edit sources from the cd seemed to include two different
versions of a map editor. the sources i've left here seem to most
closely match the version of mapedit.exe included on the book's cd
Gered