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
What feature or change would you like to see made?
We would like to inquire whether Cornerstone3D provides a method for its consumers, such as the OHIF viewer, to determine whether a segmentation has been modified. If so, the consumer could perform specific actions or provide UI feedback, such as enabling or disabling a button or displaying a save confirmation dialog.
We have noticed a dirty flag is used here. However, it does not appear to be set appropriately because the segmentIndicesCache is not set. Should this flag be managed by Cornerstone3D itself?
Will this flag be a part of the public API in Cornerstone3D 2.0?
If not, what is the recommended approach for determining whether a segmentation has been modified?
In our use case, we want to employ the isDirty flag to determine whether to enable the save button in the segmentations panel. We can employ the dirty flag, if available, to inspect the state of a segmentation to determine whether it has unsaved changes. Can you please advise how we can proceed with such an implementation?
Why should we prioritize this feature?
This feature would be a valuable addition to the product consumers.
It would provide better UX feedback on button state, and prompt users to save modified segmentations before navigating away from the viewer to prevent accidental data loss.
The text was updated successfully, but these errors were encountered:
What feature or change would you like to see made?
We would like to inquire whether Cornerstone3D provides a method for its consumers, such as the OHIF viewer, to determine whether a segmentation has been modified. If so, the consumer could perform specific actions or provide UI feedback, such as enabling or disabling a button or displaying a save confirmation dialog.
We have noticed a dirty flag is used here. However, it does not appear to be set appropriately because the segmentIndicesCache is not set. Should this flag be managed by Cornerstone3D itself?
Why should we prioritize this feature?
This feature would be a valuable addition to the product consumers.
It would provide better UX feedback on button state, and prompt users to save modified segmentations before navigating away from the viewer to prevent accidental data loss.
The text was updated successfully, but these errors were encountered: