Here's a longstanding 'come and go' problem with LB's frame bmp save option that affects the latest rev:
If you save a frame as bmp, the write protect bit is set (SOME prev revs did this, too); as a consequence,
when you save a new frame using the same filename, LB goes through the motions, but the file is not updated.
Wave rendering has never done this, as I can remember.
And another one- if you set the output bmp size to an oddball number like 1001 square, it has the familiar
old-time TV 'horizontal hold' problem. Having the experience of working with bmp for awhile, it looks like a
'junkbyte' problem. I tried running LB itself at oddball sizes, and did not encounter this issue- I had the
impression that LB uses the same 'bitmap-class object' stuff for screen and bmp??? While we're at it, if I
change the screen background color in LB, it does not affect bmp generation, as is done in LW... Actually,
all visual related settings in LW (labeled in blue text) affect both screen and bmp.
