The ActiveBuildMenu would, when returning to the first screen of 4 choices, reset the current itemIndex back to 0.  Appearance was scrolling to the next screen, then moving up one and having the current item suddenly be the top of the list.  This occurred because when redrawing the first four items, the pause item would invoke resetState() to get correct pause info.  However, resetState() was unnecessarily setting itemIndex=0.  Unnecessary since that's both the default and that particular menu never needs to tweak it anyway
Merge pull request #6 from jetty840/dcnewman-merge

The ActiveBuildMenu would, when returning to the first screen of 4 choic...