Search Results

It's actually a structure, or a struct that is defined in the bmp.h file: /** * RGBTRIPLE * * This structure describes a color consisting of relative intensities of * red, green, and blue. * * …

I would wager that you looked at the images but not at the raw data in the files. Since the header is correct, it tells any bmp viewer to display the amount of data that should be in the image, but if …

The main problem is that the code doesn't copy the struct data from the original header structs bi and bf to the new ones, new_bi or new_bf. That means that the headers that are written to the output …

Several issues here. First, look at the code that expands the line horizontally: for (j = 0; j < biSmall.biWidth; j++) { // read RGB triple from infile fread( …

This is code from the original copy.c program that will later be used in resize. An fseek call will cause the file pointer to change position in a file. You should google it and study the details. I …

So close indeed!!! I'll give you a hint. When you're working with an open file, are you sure that you're using values appropriate for the right file? In other words, input file vars when working wi …

I'm going to assume that you haven't added any code yet to scale the actual image data yet. I ran your code and it seems to be correctly handling the headers. Perhaps you're executing a different ve …

So, I see that it calculates the padding for the input file. Where is the padding calculation for the output file? They are not necessarily the same, especially if the scaling factor != 1. Also, bi …

There are two major issue. First, the code is using biWidth and biHeight for the output file to control reading from the input file. Second, there's no actual code to handle vertical scaling. Per …

You've clearly looked at the images generated, but have you looked at the raw image data using the xxd tool? It's a lot more revealing because you can see patterns in the raw data! There are a couple …

Actually, you don't get the correct image size. The output image data is several times larger than it should be. The intent of the code posted above is to read in a pixel (an RGBTRIPLE), copy it to a …

First, there are errors in calculating header data. That should be easy to fix. The design logic for vertical scaling is totally flawed. Understand that images are not stored in two dimensions. The d …

The code will work when the scaling factor is 1, but not otherwise. The problem is straightforward. The code calculates the new biHeight and biWidth values, but it doesn't plug them back into the …

Looks like too many loops. Why is there an outer loop that processed the entire input file n times? Most of the pieces are there, but reprocessing the entire file more than once won't accomplish an …

This line has a couple of problems: scanline[pixel + n] = triple; Let's say that the scale factor, n, is 3. Now, let's walk through what happens. The code starts by reading the first pixe …