You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 11, 2021. It is now read-only.
Currently, there's two resolution policies - one for a CCScene and another for CCViewport. The CCScene ultimately sets up the correct exact fit viewport rect based on:
specified design resolution
CCScene resolution policy
which are specified in CCWindow.SetDesignResolutionSize and then afterwards the Viewport scales the exact rect to get the actual rect based on the CCViewportResolutionPolicy which can be one of either:
ExactFit
AspectFill
AspectFit
By default the CCViewport is created with an ExactFit policy meaning no subsequent scaling is performed.
But there is no need (and in fact it's confusing) to further specify an additional viewport resolution policy which subsequently scales the exact bounds. Instead, a user can simply set a different design resolution to get the exact fit bounds they want.
As an analogy, it's like setting int x=4; x = x /2; vs. int x = 2;
The text was updated successfully, but these errors were encountered:
Currently, there's two resolution policies - one for a CCScene and another for CCViewport. The CCScene ultimately sets up the correct exact fit viewport rect based on:
which are specified in
CCWindow.SetDesignResolutionSize
and then afterwards the Viewport scales the exact rect to get the actual rect based on theCCViewportResolutionPolicy
which can be one of either:By default the CCViewport is created with an ExactFit policy meaning no subsequent scaling is performed.
But there is no need (and in fact it's confusing) to further specify an additional viewport resolution policy which subsequently scales the exact bounds. Instead, a user can simply set a different design resolution to get the exact fit bounds they want.
As an analogy, it's like setting
int x=4; x = x /2;
vs.int x = 2;
The text was updated successfully, but these errors were encountered: