2. A "callback function" is an event handler. The openGL needs to know which event handler to use when an event occurs (or, when an event is fetched from the event queue). The process of "callback function registration" is for that purpose. A user is allowed to register more than one callback function for the same event type. If a user registers more than one callback function for a particular even type, the most recently registered callback function will be called when an event of that particular type occurs. This is implemented using the "over-writing" technique. Do you have a way to handle such a situation without using the "over- writing" technique? (10 points) If "clipping" is not done before the window-to-viewport mapping, one would get the so-called "internal register overflow" problem. This "internal register overflow" problem would then cause the "wrap around" phenomenon. Do you have a way to overcome the "wrap around" phenomenon without doing the clipping process? (10 points) 3. 2. A "callback function" is an event handler. The openGL needs to know which event handler to use when an event occurs (or, when an event is fetched from the event queue). The process of "callback function registration" is for that purpose. A user is allowed to register more than one callback function for the same event type. If a user registers more than one callback function for a particular even type, the most recently registered callback function will be called when an event of that particular type occurs. This is implemented using the "over-writing" technique. Do you have a way to handle such a situation without using the "over- writing" technique? (10 points) If "clipping" is not done before the window-to-viewport mapping, one would get the so-called "internal register overflow" problem. This "internal register overflow" problem would then cause the "wrap around" phenomenon. Do you have a way to overcome the "wrap around" phenomenon without doing the clipping process? (10 points) 3