Build 0206

Includes the following:

 - Add options for detailed debug logging in somedit config.
   Detailed logging added for music and map pieces for now.
 - Fix bug that caused music to overwrite part of the world map.
 - Fix bug that caused an audio glitch in the town theme.
 - Fix bug in event editor where closing the popup with the "X"
   instead of the cancel button caused problems.
 - Fix bug that caused unknown/raw event editor to throw exceptions
   a lot when you cycle through the type.

https://dl.dropboxusercontent.com/u/19968993/som/FileListing.html

https://dl.dropboxusercontent.com/u/19968993/som/build%200206/somedit0206.rar

https://dl.dropboxusercontent.com/u/19968993/som/release_notes.txt

Next up: refactoring how they store their triggers.  These are the spots on a map that cause things to happen, like door transitions, or events.  Right now it's 2 bytes each, with a flag for whether it's a door or an event, then the index for which one.  There is no x or y.  The position is determined by seeking all the way down the map, looking for tiles of a certain type, and placing the triggers one by one in the map load routine.  This is accomplished by changing the tile value to 0xC0 (the upper limit of actual tile values) through 0xFF.  If you step on a tile with a value >= 0xC0, it executes the trigger (value - 0xC0).  Why anyone thought this would all be a good idea or how they designed their maps under a system like this are beyond me.

The new plan is to expand triggers from 2 bytes each to 4 bytes each, with a new x and y value for each.  The existing loop over every tile will be removed, and replaced with a loop over every trigger, that will simply write the trigger 0xC0+ marker value as it is now at the associated x,y based on the two new bytes.  Everything else should work the same as it does now after that point.

This should make map editing a lot easier, since you can just place triggers wherever the hell you want.