The goal of this programming assignment is to give students experience with OpenGLs user interaction call back functions. Your task is to design and implement a program that allows the user to create and display a collection of solid color rectangles.
Users of your program will use the mouse to specify two corners of a rectangle (click down for one corner, drag, click up for other corner). These (x,y) coordinates must be stored in a global data structure of some sort. Your program should display this rectangle as a solid color.
Users should also be able to use the keyboard to specify the (r,g,b) color for the rectangle. For example, clicking on 'r' or 'R' might decrease or increase the amount of red in the rectangle. The tricky part is deciding which rectangle to color. One option would be to adjust the color on the last rectangle created. Another option would be to use the (x,y) coordinates of the mouse when the keyboard is clicked to select the correct rectangle.
Finally, Your program must also be able to write/read rectangle information to/from ASCII files. The format of the file is up to you. Select one character to read the file, and another character to write the file.
You can implement this program using either a bottom-up approach or a top-down approach. If you go for a bottom-up approach, start by creating basic methods and classes, and test theses methods using a simple main program that calls each method. When this is working, you can create the main program that uses these methods to solve the problem above.
If you go for a top-down approach, start by creating your main program that reads user input, and calls empty methods to pretend to solve the problem. Then add in the code for these methods one at a time. This way, you will get an idea of how the whole program will work before you dive into the details of implementing each method and class.
Regardless of which technique you choose to use, you should develop your code incrementally adding code, compiling, debugging, a little bit at a time. This way, you always have a program that "does something" even if it is not complete.
Test your program to check that it operates correctly for all of the requirements listed above. Also check for the error handling capabilities of the code. Try your program on 2-3 input documents, and save your testing output in text files for submission on the program due date.
When you have completed your C++ program, write a short report (less than one page long) describing what the objectives were, what you did, and the status of the program. Does it work properly for all test cases? Are there any known problems? Save this report in a separate text file to be submitted electronically.
In this class, we will be using electronic project submission to make sure that all students hand their programming projects and labs on time, and to perform automatic analysis of all programs that are submitted. When you have completed the tasks above go to the class web site to "submit" your documentation, C++ program, and testing files.
The dates on your electronic submission will be used to verify that you met the due date above. All late projects will receive reduced credit (50% off if less than 24 hours late, no credit if more than 24 hours late), so hand in your best effort on the due date.