Search Results

If you resize that by 2, (see where this is going?) a scanline will be 6px or 18 bytes, which requires 2 bytes of padding. …

Zamyla gives psuedocode for two methods to resize vertically in the walkthrough (starting around 8:30). This code looks more like the "recopy" method. …

I see a problem here: for (int l = 0, k = j * times; k < times; k++, l++){ Arr[k] = triple; } The intention is to put times copies of triple into Arr. Let's say you are …

Here's the psuedo code from the walkthrough: psuedocode: "recopy" method for each row      for n-1 times           write pixels, padding to outfile           send …

Problem 1: fseek(inptr, (54+ bi.biWidth * sizeof(RGBTRIPLE) + paddingoriginal)*i, SEEK_SET); 54 is for all intents and purposes, a constant. Problem 2: It is writing out the headers of the original i …

There's a problem here: line[j + l] = triple;. Using an infile width of 3 and a factor of 3: When j is 0, this will populate indexes 0,1,2. When j is 1: indexes 1,2,3. When j is 2: indexes 2,3,4. B …

From the walkthrough: psuedocode: "recopy" method for each row      for n-1 times           write pixels, padding to outfile           send infile cursor back[1] …

There's a problem here long var = new_bi.biWidth * sizeof(RGBTRIPLE);. This will "rewind" the input file pointer too far.

There is a unix shell command called resize. It looks like you invoked that with your valgrind command, something like valgrind resize 2 small.bmp bigger.bmp instead of valgrind ./resize ..... …

fffffff4 in hexadecimal equals.......4294967284 in decimal

One problem in the k loop: It is adding padding each time it duplicates a triple instead of one time when it is done with the line. If you 2x small.bmp it will: read a triple, write two triples, writ …

FILE header comes before INFO header. Make sure you output (fwrite) them in the correct order.

fseek does not require an unsigned long, the signature is int fseek(FILE *stream, long offset, int whence); The runtime error stems from this calculation -((bi.biWidth * sizeof(RGBTRIPLE))-1). size …

The headers of the new image have biSizeImage and bfSize values of the original.

A quick way to format code properly: select the code and click the {} in the format bar, to-da. This can be done on initial post or you can edit the question and fix the format. Here is the pseudo co …