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

Hide find_largest_segment_id job button unless category:segmentation is already saved #8348

Open
fm3 opened this issue Jan 22, 2025 · 0 comments

Comments

@fm3
Copy link
Member

fm3 commented Jan 22, 2025

Looks like you can start the job after selecting category:segmentation in the dropdown, even without saving. The job then fails, if on disk the layer still has category:color.

Can we guard against this in the frontend?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant