Forum unknown
· Programming
#'veloper's blues
3 messages in this thread
There is a bug in 1.0/1.1 kickstart. After using ScrollLayer, calls to
MoveLayer/SizeLayer may trash your bits. It is fixed for 1.2 The 1k limit is
the blitter limit. It can only do blits of about 1k by 1k. Actual limit may
be 16 pixels less because of shifting during blitting. The architecture of
the display is not limited to 1kx1k however the NTSC standard has it's own
limitations.
Thanks, a bug like the one you mention in ScrollLayer might explain my
smearing problem. But it doesn't sound as if it explains my
clip-at-left-butnot-at-right problem for text of smaller widths in still
smaller windows. It's funny, what you say about the blitter limitation. I
had already changed the maximum width of my superbitmap from 1024 to 1008,
after experiments showed that I lost 16 pixels of data scrolled just up to
the 1024 boundary (with ScrollRaster), where it should have been okay.
So when do we mortals (developers and others) get version 1.2?
Thanks, a bug like the one you mention in ScrollLayer might explain my
smearing problem. But it doesn't sound as if it explains my
clip-at-left-butnot-at-right problem for text of smaller widths in still
smaller windows. It's funny, what you say about the blitter limitation. I
had already changed the maximum width of my superbitmap from 1024 to 1008,
after experiments showed that I lost 16 pixels of data scrolled just up to
the 1024 boundary (with ScrollRaster), where it should have been okay.
So when do we mortals (developers and others) get version 1.2?