@kike One issue with this is that when used in conjunction with ‘Add 3D view’ it causes problems when the settings change and tracking is set to Reconstruct.
For example, if I create a view, lock the views and then modify the views I get an error saying that the view is locked. Ideally what would happen is that if the view is locked AND tracking is set to Reconstruct, the view is unlocked first and then updated.
OR alternatively, locking is built-in the ‘Add 3D view’ component.
If I created a view manually and locked it, I would expect that the lock operation is the dominate control. However, if I create a view with RIR and lock it downstream, I would expect that the view create is the dominant control.
I guess it comes down to separate transactions and their sequence. The way that I have it as two separate transactions means that once the view is locked, I can’t re-run the script easily. What I would need to do is collect all the views, filter them out, unlock them and then re-run the original script.
Although looking at it again, even if the views are locked, views are still output from the add 3d view component, so I can undo the lock after they are created. But it is still a bit awkward.
I guess if we could combine it into the same transaction, i.e. with Add 3D view, this would simplify the workflow. Just a thought…