BGI graphics in C.

[DeSeis]

Hi
Im doing a little crap thing for school.
I used the putimage, getimage with XOR etc to put stuff arround the screen. Did it like that :

unsigned char *buff[6]; <<< buffer for the images that are saved
from the screen.

and used the getimage like this:

getimage(x,y,x2,y2,buff[1]);

at that point it saves it to buff 1 and when i use
putimage(x,y,buff[1],COPY_PUT); it goes out ok.

but if i will add another getimage (for another image) it will like destroy all last saves in the buffer and overwrite it over all the array. so when i will use putimage(buff[1]) i wont get the one i saved at the first place, i will get the last thing i saved (even when it is saved on another buff (like buff[5]

Any idea?!
its killing me.
Thanks

[Salem]

> getimage(x,y,x2,y2,buff[1]);
Before you do this, you need to allocate some memory

Perhaps like this....
buff[1] = malloc ( (x2-x)*(y2-y) );

BUT!!!
check the manual page, to ensure you allocate enough memory for the amout of data getimage will write.

[DeSeis]

Well i did something like that:

buff[3]=malloc(20*20);

i get:

cannont convert *void to * unsigned char *

[quzah]

Apparently your compiler wants a cast.

buf[x] = (unsigned char *) malloc( 20*20 );

Quzah.

[DeSeis]

Thank u brothers.

[DeSeis]

My object size is 20*20 in pixels.
isnt it too much to allocate 400?!
Coz i get weird results after 1st..

buff[1] getting ok.
buff[2] is fuxored.
buff[3] is ok.
wtf?
whats going on?
i Set all to allocate 400.

example:
buff[i]=(char *)malloc(400);
..

[Salem]

> cannont convert *void to * unsigned char *
Try compiling this using a C compiler, and not a C++ compiler.

Renaming your source files from .cpp to .c is usually a good start.

> My object size is 20*20 in pixels.
Are you sure it's not 21*21 ?

Like i mentioned previously, RTM!!!

getimage(0,0,20,20,buff[1]);
might be copying a 21*21 pixel image, which would definitely cause you a problem, if you thought that 20*20 was enough.