Florian M

I agree with Philipp that annotating with fallback layer is not completely replaced by the multiple annotation layers. Because of this I too am uncertain whether simply removing the requirement...

Sounds fair to me. So this modal would have to pop up when the user wants to take the very first brush stroke in a volume layer with fallback segmentation,...

#6330 added a button to add layers. Renaming this to track the delete layer button

quoting philipp from duplicate #6482: > In case the layer is based on a fallback layer, the naming should probably be "restore original segmentation layer (warning: this will delete all...

@philippotto Would you be interested in implementing the front-end todos here? @jstriebel Would you be interested in adapting the python client? I think the important part is that the segmentation...

@philippotto I changed the proto file to allow None for largestSegmentIds. Note that in the update actions they are still not nullable. When I tried to create an empty volume...

I was still assuming that volume annotating was essentially impossible while no largestSegmentId exists. But from what you mentioned in the meeting, it sounds like you want to only forbid...

Yes, I’d say the backend is also ready for review. I tested the behavior and it makes sense to me. However, I’d suggest that we explain to the user a...

@jstriebel Thanks for having a look! This is why reviews are important, this code was really quite cryptic :D I added some comments now, hopefully answering your questions. I also...

for elementClass, yes, but the largestSegmentId would already be nice, I think