You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, an annotation can have multiple "tracings" (skeleton, volume, editable mapping). All of these have an isolated version history. The UI also exposes these separately, which can be very confusing to deal with from a user perspective. While we could adapt the UI so that only one virtual version history is presented, it might make sense to change the underlying structures. We should draft a design doc and discuss how to proceed.
Currently, an annotation can have multiple "tracings" (skeleton, volume, editable mapping). All of these have an isolated version history. The UI also exposes these separately, which can be very confusing to deal with from a user perspective. While we could adapt the UI so that only one virtual version history is presented, it might make sense to change the underlying structures. We should draft a design doc and discuss how to proceed.
https://www.notion.so/scalableminds/Design-Doc-Unified-Annotation-Versioning-d43efa620adc4a6080a15e689a82b907
The text was updated successfully, but these errors were encountered: