Closed joshtynjala closed 12 years ago
Doesn't this also imply a lack of Starling core to represent both a ScaleFactorX and ScaleFactorY too? (along with not scaling textures differently in both dimensions if necessary?)
It would be nice if Starling exposed the Y value too, or at least provided a way for me to get the viewPort without creating a clone of the Rectangle. Even if the direct mViewPort value weren't exposed, then at least it should allow me to pass in my own Rectangle to populate.
Beyond that, I don't really have an opinion because I still don't use this feature.
Understood, also I think most people, myself included, always set stageWidth/Height and viewport Width/Height to the same ratio, so I would never see different scaleFactors for X and Y. I wouldn't ever want that to happen in my app.
contentScaleFactor returns this value: mViewPort.width / mStage.stageWidth
However, the scissor rectangle's y and height need to be scaled by this different value: mViewPort.height / mStage.stageHeight