Every program we wrote was preceded with: #include TRUE OR FALSE To make a screen of $($say$)1000$x$1000$ pixels more manageable in terms of graphics, one principle we use $($in some programs$)$ in our class coding in C$++$ is to just treat it as cells of say $10$x$10$ or $20$x$20$ or $40$x$40...$or upto $100$x$100$ and then use discrete rather than continuous motion.

$\_\_\_\_4.$ Single buffering improves smooth continious motion rendering and reduces flick.

By having fewer buffers, you can focus on the screen state and appearance, rather than wasting compute time on many buffers all over the place. Taking care of two buffers cuts the time you have on the screen buffer in half. For quality animation, a single buffer streamlines the rendering and focusses on that single screen. Double buffering was only needed in the past.

$\_\_\_\_5.$ VGA graphics modes provide all the screen resolution we need.$$ The human eye cannot see higher resolution than VGA from $1987,$ henceVGA is the standard even now.

$\_\_\_\_6.$ True color $(24$ bit color pixels$)$ provides the maximal color needed for all human vision.$$

The human eye can only see a subset of the