calling ofEsayCam::disableMouseInput() during setup results in different initial camera position

When starting an app with an ofEasyCam, by default the camera will automatically move to (0,0, (approximately ofGetWidth()/2) ).

However, if you call disableMouseInput() in setup, the camera will start at (0,0,0) instead.

This is somewhat confusing. The default position should be the same regardless of whether disableMouseInput() is called or not.

class ofApp {
...
ofEasyCam mCamera;
};

void ofApp::setup() {
    //mCamera.disableMouseInput();
}

void ofApp::update() {
    ofLog(OF_LOG_NOTICE, "camera at %s, orientation %s", ofToString(mCamera.getPosition()).c_str(), ofToString(mCamera.getOrientationQuat()).c_str());
}

result with above code at 1600x900:
[notice ] camera at 0, 0, 779.423, orientation 0, 0, 0, 1

result after uncommenting disableMouseInput:
[notice ] camera at 0, 0, 0, orientation 0, 0, 0, 1

Start by tracing ofEasyCam initialization from the ofApp::setup() entry point, comparing the default path with a call to disableMouseInput(). Reproduce both cases using the supplied 1600x900 example and compare the logged position and orientation. Done means both paths produce the same initial camera position and orientation.