If an ipyniivue.Niivue instance has already been displayed and then is displayed again in a different cell, the older display becomes non-interactive. The reason for the current implementation is multifold:
1) any callbacks and states for the NiiVue instance will be saved (ie transferred to each new NiivueView)
2) previous views of the NiivueModel will be saved (frozen/non-interactive). This allows for viewing progress over cells.
The reason for marking this as enhancement is for others to provide ideas for this feature (if there are use cases that require syncing behavior).
If an ipyniivue.Niivue instance has already been displayed and then is displayed again in a different cell, the older display becomes non-interactive. The reason for the current implementation is multifold: 1) any callbacks and states for the NiiVue instance will be saved (ie transferred to each new NiivueView) 2) previous views of the NiivueModel will be saved (frozen/non-interactive). This allows for viewing progress over cells.
The reason for marking this as enhancement is for others to provide ideas for this feature (if there are use cases that require syncing behavior).