Track Gap Revisited


Now it is possible to have a gap of 1...4 bytes used as a self-repeating stream, or a 1...2 byte different stream for the track gap, before and after the overlap position.

Old code related to this was almost completely rewritten to use a much more elegant and readable solution, it was getting way too complex.

A previously unused block property is now used as a placeholder of various block specific encoding/decoding attributes.

This is still mostly useful for automated MFM script generation. Although it is possible to create a similar effect using scripts, this is a much cleaner solution that is not a function of disk/track specific values of a certain dump, thus the script generator can be kept generic.