Thread: create a console based application in c language that can join and split bitmap image

i have to create a console based application in c language that can join and split bitmap images.
can anyone help me with the code.
the requirements of the application are as follows :

1. Split Image

Enter number of parts:

Enter source image path:

Enter destination folder:

2. Join Images (all images should be of same width and height)

Enter image path:

Join more Image (y/n):

3. Exit



Take care of following things:

· Application should show number of images processed while running.

· Acceptable Image format is BMP only.

· Application should give all the validations for correct image name, type, size, path, etc.

> can anyone help me with the code.
We can help, but we can't write it for you. So you need to show us what code you have and tell us specifically what problems you are having. Then we can help you.


To help you get started, read this: Bitmap - Wikipedia, the free encyclopedia. It helps to realize that a bitmap is just a 2-d array of pixels, along with some header info, so merging/splitting them is the same as you would do with any 2-d array.

Lastly, it's important to approach this in an organized manner.

1. Think about how you would do this "on paper", i.e. without a computer. Validate this by testing it out with some hand-made "bitmaps" (perhaps using graph paper, and small images, say 3x3 up to 10x10). You can't program the solution to a problem if you can't solve the problem in the first place.
2. Break the problem up into reasonable smaller problems: process command line options; validate image names, types, sizes, paths, etc.; read the bitmap image into a 2-d array; write a 2-d array back to a bitmap file.
3. Take careful note of each minute step you take along the way, those steps will form your algorithm.
4. Turn those steps to pseudo code.
5. Turn that pseudo code into real code, little by little.
6. Remember to work in small chunks. Implement 5-10 lines of code, compile (make sure you get no warnings with warning levels set to max), and test. Never move on to the next section of code before you fix all the issues with what you currently have.