Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reloading meshes on edits does not follow subsequent user interations #545

Open
ceesem opened this issue Apr 28, 2021 · 0 comments
Open

Comments

@ceesem
Copy link

ceesem commented Apr 28, 2021

It can take several seconds (at least) for edits to go through the pychunkedgraph. During that time, a user can deselect a neuron that is being merged/split, request a new edit, or make other changes that affect what root ids are selected in the scene. However, Neuroglancer does not respect these user events when handling the response from the chunkedgraph edits. For example, if I make a merge and deselect both objects, the subsequent merged root id will become selected even though it no longer replaces anything in the state. Similarly, making a second split edit (on a different object) will often cause an inconsistent mesh loading, often not actually doing the replacement expected.

chrisj pushed a commit that referenced this issue Apr 2, 2024
Bumps google.golang.org/protobuf from 1.30.0 to 1.33.0.

---
updated-dependencies:
- dependency-name: google.golang.org/protobuf
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant