Change order of if conditions so that constant precedes operator

This is a syntactic trick for C/C++ programs in which you can use an assignment statement as an expression. By putting the constant before the operator, you cant use the statement as an assignment if theres a typo and == becomes =. valid code  could still be valid should this typo occur  and few would be the wiser. To fix this, simply re-order the expression:
refactor RenderShowFrameNumberScrolling

including saner code style, micro-optimization, and comments
change text argument of RenderShowFrameNumberScrolling to int

since RenderShowFrameNumberScrolling will (and should) only render an integer value onto the frame buffer
add code to outline frame number in RenderShowFrameNumberScrolling()

To fix issue #4, I added a patch to outline the frame number in the RenderShowFrameNumberScrolling.