Detangle CesiumCameraController
from CesiumFlyToController
#434
Labels
quality
Improve code quality or encourage developer success
The changes in #422 raise some implications about our current component design that I think we should consider, to improve code quality and clarity.
While working with XR, @azrogers found a scenario where:
CesiumGlobeAnchor
, butCesiumCameraController
andCesiumFlyToController
.It feels conceptually strange that the
CesiumFlyToController
is piloting a parent object, or more generally some object that it isn't actually attached to. Historically we have attached it to a camera in order to make it fly between locations, but we should look to decouple this fromCesiumCameraController
. Cesium for Unreal does this and also seems to account for movement interruption, so maybe we can take the implementation from there.There may be more design implications to consider, but I can't remember completely what we discussed offline. @azrogers feel free to weigh in if I missed anything!
The text was updated successfully, but these errors were encountered: