just an fyi:
I've been painstakingly working on updating mike's macro file for metallica for the past 6 weeks (1.63 to 1.64) and am finally getting close to having it complete. after I'm done, I plan on going back and coloring the unfinished sections (like 'the end of the line')
they shifted the frame numbers between these versions which is why it has taken me so long to shuffle everything (frame by frame) as well as putting all of the frames in order
during the process of doing this I've noticed the following things with the pinball browser macro functionality. optimize does not do what you might think it does. it merely collects all of the [multiple] instances of a particular frame and groups them together within a set of the { and } brackets
all instances of coloring, re-coloring and flood fills of the same pixel location are kept, meaning that if you have something like this:
EditImage,0x5BF
{
Pen,17,47,0,0,1,4,15
Pen,17,47,0,0,1,7,15
Pen,17,47,0,0,1,4,15
Pen,17,47,0,0,1,3,15
FloodFill,17,47,0,0,1,7,15
}
after choosing to optimize it, the result is be exactly the same as above. the optimize functionality does not remove duplicate commands that act upon the same pixel location (keeping only the last instance of coloring (pen and/or flood fill)
if you decide to color something one way, and then change your mind and re-color it a different way, all of the changes remain in the macro file (meaning that the file becomes larger and will take longer to run)