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
Using cameraComponent.setBounds(), the camera still renders out of bounds components. This happens because the BoundedPositionBehavior object only prevents the center of the view finder to go out of the screen.
I think it's nicer to not render empty space, as it was the case with the old camera object.
Note that this is the intended behavior, as discussed in #2564.
Why should this be improved
Well, it would be nice for the camera to not render empty space.
Any risks?
No risk. I think the best way to do it would be to create a cameraComponent.calculateVisibleWorldViewfinderBounds() or something like that, so that it can be used alongside of cameraComponent.setBounds().
The text was updated successfully, but these errors were encountered:
What could be improved
Using
cameraComponent.setBounds()
, the camera still renders out of bounds components. This happens because theBoundedPositionBehavior
object only prevents the center of the view finder to go out of the screen.I think it's nicer to not render empty space, as it was the case with the old camera object.
Note that this is the intended behavior, as discussed in #2564.
Why should this be improved
Well, it would be nice for the camera to not render empty space.
Any risks?
No risk. I think the best way to do it would be to create a
cameraComponent.calculateVisibleWorldViewfinderBounds()
or something like that, so that it can be used alongside ofcameraComponent.setBounds()
.The text was updated successfully, but these errors were encountered: