List of Known Bugs and Issues

-	deleting lines from long fragment program could cause problems during
	stepping if the program counter is set beyond the length of the new program. 

-	window size needs to follow application

-	We don't detect NV30 RC/HC when instruction is conditional update (ie ADDC R0, R1, R2; etc)

-	Interpolants are not visualized

-	Error reporting under NVidia (for recompile/interpret) is not very helpful because
	it does not highlight error.

-	Adding variable to fragment program does not refresh dropdown list

-	State of buttons in the toolbar does not adequately reflect current state (edit, paste, etc)

-	The following buttons and window items do not work:
	save, save as, file->exit, file->save, file->saveAs, print, Cntrl-Y

-	Find window has only partial functionality (do not use)

-	visualization fragment program will only run when the register being watched has
	been modified before the current step.

-	on certain systems, the bottom line of the edit box is dropped.

-	require all state to be set in the draw loop.  we should expose an init() which will allow
	user app to initialize state beforehand.
 
-	catalyst 3.8 is broken -- 3.7 works just fine

-   problems are encountered when user uses result.color as the output instead of specifying an 
	OUTPUT variable.  Workaround is to declare an output variable using OUTPUT.

-	Ap. must have active redraw loop (ie glutIdleFunc posting redraw) or debugger does not redraw.