Problem
Tracing while a zarr image is still loading can orphan the traces: they are placed against a section state that the load then replaces, so the drawing is lost or left detached from its section. This is a data-integrity issue, not a cosmetic one (from the legacy wishlist, PHP request 6).
Proposed
Block tracing until the zarr load completes, or warn and discard input during the load window. Either way the field should not accept traces it cannot reliably attach.
Part of #66.
Source: PyReconstruct Wishlist, PHP Requests #6.
You can make traces when the zarr is not done loading yet, so that when the zarr finishes loading, the traces are no longer on the object. It would be nice if it was impossible to make traces during this time, maybe with a message stating the reason.
Problem
Tracing while a zarr image is still loading can orphan the traces: they are placed against a section state that the load then replaces, so the drawing is lost or left detached from its section. This is a data-integrity issue, not a cosmetic one (from the legacy wishlist, PHP request 6).
Proposed
Block tracing until the zarr load completes, or warn and discard input during the load window. Either way the field should not accept traces it cannot reliably attach.
Part of #66.
Source: PyReconstruct Wishlist, PHP Requests #6.