Florian M

Thanks for having a look and thanks for pushing the change in the python client! Do you think we should wait for some days before deploying this, so that more...

The transaction grouping is not currently stored in the db, it is only used to hold back its update groups until the transaction is complete, then they are all inserted...

Node positions are stored as three integers in the protobuf definition (see [here](https://github.com/scalableminds/webknossos/blob/master/webknossos-datastore/proto/geometry.proto#L6) and [here](https://github.com/scalableminds/webknossos/blob/master/webknossos-datastore/proto/SkeletonTracing.proto#L9)) I’m pretty sure that this was by design at some point. Do you think it...

I agree with your three options. In order to decide whether a is good enough, I’d like to ask: How are z coordinates handled when creating a node in the...

Mouse position is 2d, though, so this does not specify which z coordinate is used, if I click on the XY viewport, I think? I’m asking with https://github.com/scalableminds/webknossos/issues/5653 / https://github.com/scalableminds/webknossos/issues/5233...

Alright, thanks :) I think it would be better to do b then, for the moment, since this change on reload can be confusing/disappointing. b should be fairly easy to...

Fair point :thinking: Do you know if there is an easy way to search the code for the information which modals have this and which don’t? Then we could discuss...

The backend part of this works now, frontend logging shows that the bbox in the volumetracing proto object is set to the fallback layer bbox. However, I noticed a few...

Thanks for investigating! I think it would be worth tackling these two to three issues, but it certainly does not have the highest priority. I guess I’ll let this PR...

This one is not actually solved by #826