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

[Feature Request] New deploy level config: Force global segmentation panel #4784

Open
james-hanks opened this issue Feb 14, 2025 · 0 comments
Assignees

Comments

@james-hanks
Copy link

james-hanks commented Feb 14, 2025

What feature or change would you like to see made?

New deploy level config: Force global segmentation panel

Why should we prioritize this feature?

Currently the segmentation panel is fixed to display current stack viewport segmentation. If switching to another active viewport with no segmentation, nothing is displayed in the segmentation panel, even if an inactive viewport does have a segmentation.

We should allow a deploy level config that enables the segmentation panel to display all segmentations regardless of active viewport. For now, this will only force display all global segmentations, new design will be required outside of scope for better UI/UX to handle scenarios where the panel needs to display conflicting segmentations.

Feat request from Flywheel meeting

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

2 participants