Models can already be dynamically added and removed. Corresponding BCF viewpoints however don't yet respond to props changing. It might be worth refactoring the model and viewpoint loading logic in such a way that the two are more coupled. So instead of having a separate models and bcfViewpoints prop, we could instead have one which includes both a model and its corresponding BCF viewpoint. Thus when changing models, updating the respective viewpoints as well could be a whole lot easier conceptually and implementation wise too.
After a boatload of trial & error and some investigation, I have found that BCF viewpoints are more tied to the scene object itself rather than the models on the scene. They seem to be only connected to models in that a selection array of objects can be supplied to select entities on models.
As a result, I propose that instead of a bcfViewpoints prop that accepts an array of viewpoints, a bcfViewpoint (singular) prop be implemented that accepts one viewpoints obejct.
Models can already be dynamically added and removed. Corresponding BCF viewpoints however don't yet respond to props changing. It might be worth refactoring the model and viewpoint loading logic in such a way that the two are more coupled. So instead of having a separatemodels
andbcfViewpoints
prop, we could instead have one which includes both a model and its corresponding BCF viewpoint. Thus when changing models, updating the respective viewpoints as well could be a whole lot easier conceptually and implementation wise too.After a boatload of trial & error and some investigation, I have found that BCF viewpoints are more tied to the scene object itself rather than the models on the scene. They seem to be only connected to models in that a selection array of objects can be supplied to select entities on models.
As a result, I propose that instead of a
bcfViewpoints
prop that accepts an array of viewpoints, abcfViewpoint
(singular) prop be implemented that accepts one viewpoints obejct.