Tweet
GRAPHIC BITMAP LOAD appears to do an automatic stretch to fit the size specified in the call. This is not documented. Is this the way the call is supposed to perform?
-
Walt Decker -
It is documented that that is the size of the bitmap you are going to create. Are you retrieving the bitmap size from the file before you load it?Adam Drake
PowerBASIC -
Graphic Bitmap Load
Yep.
But, it would seem to me that if the source *.BMP is larger than the memory bitmap it would stop loading when the size of the memory bitmap is reached instead of shrinking the source. On the other hand, if the memory bitmap is larger than the source the source should not be expanded to fit the memory bitmap. Those should be left to GRAPHIC STRETCH or GRAPHIC RENDER.
Unlike GRAPHIC RENDER and GRAPHIC STRETCH, the documentation for GRAPHIC BITMAP LOAD does not state that the source will be expanded or shrunk to fit the memory bitmap.Walt DeckerComment
-
It does not specifically state that the bitmap will be stretched to fit, you're right, all I read there is:
I'm not sure if the stretch would be expected behavior or not, however it would seem it is, and it might need to be stated in the help file.The parameters nWidth& and nHeight& specify the width and height of the bitmap, in pixels.Adam Drake
PowerBASICComment
-
Well, I for one expected a bit to bit copy. The memory bitmap was about 20 X 10 larger than the source bitmap since I wanted to do some work on it before loading into the graphic control. Since the source was stretched I had to create a second memory map, copy the first into the second, then do the work.
It's no big deal, just some extra coding, but it was a surprise.Walt DeckerComment
Comment