Renaming Segments forces color selection as well

I used to be able to double-click a segment name in Segment Editor to change ONLY the name. Now when double-clicking, the box to change color and name both pop up, but requires me to select a color as well or else it will change to whatever color gets auto-selected. This is in 5.8.1 but I believe it was implemented in the previous stable release.

Please change it back to how it was where I could just double-click the name and change only the name!

This was introduced to promote use of standard and custom terminologies. If you want the old behavior, you can bring it back by going to Edit→Application Settings→Segmentation

and uncheck “Use standard terminologies for segments”

1 Like

Thank you! That works, although the hover message of “invalid terminology information” is annoying but I can live with it.

I haven’t seen that before, can you describe or provide a screenshot along with your slicer version/OS?

S

Slicer 5.8.1, Windows 11

This screenshot from 5.8.1, which doesn’t use the new terminologies feature. Did you create this segmentation in a recent preview and then open it in 5.8.1?

I started it in an older version and opened it in 5.8.1. I tried another old scene and I’m getting a different hover message.

This one is correct. It is simply providing more detailed information about the terminology being used.

Having said that, you should really start using your own custom terminology. That way your projects will be consistent (in terms of labels, no typos, colors) and when you extract labelmap (e.g., for machine learning or to export to other software), the conversion will be predictable. You can import a big ontology like Uberon and extract terms from there, or create your custom terminology and color table.

Here is a short tutorial I have written for SlicerMorph.

1 Like

I will look into the tutorial. Thank you!

It would not be hard not to show this warning in the tooltip if the user opted for not using terminolgies in the application settings, but it is not something I have time for right now. Feel free to add a new issue on GitHub if you would like us to do it in the next months.