Waveform combobox looks cluttered

[daschuer]

Bug Description

See:

There are to many words in braces

The non accelerated types are IMHO not legacy.

How is the state of discussion to drop legacy GLSL types?
Is "deprecated" a better word for the types that will be removed in the next version?

Version

2.4-beta

OS

No response

[ronso0]

We could group the types by (meta)type, and add plain separators, or non-selectable labels (e.g. "Deprecated:", "CPU-accelerated:")

[Holzhaus]

Can't we only list the different waveforms (RGB, HSV, Filtered,...) and determine the proper rendering variant automatically depending on what is available? Most users have no idea what to select anyway.

[daschuer]

For me, a minimal 2.4.0 solution is to get rid of the double (..) works:
RGB (GLSL)
RGB
RGB (legacy GL)
RGB (legacy GLSL)

The grouping idea sounds appealing. I would call CPU "accelerated" though. We may relpace GLSL by accelerated instead.

[Swiftb0y]

We're discussing polishing something that will be unnecessary by 2.5 anyways. Lets just keep as is to get the release out. This issue will resolve itself with the removal of the GL and GLSL types soon anyways.

[daschuer]

But at least calling the non accelerated Waveforms legacy is wrong. We need an OKish user experience for 2.4 as well.

[Swiftb0y]

sure...

[ronso0]

As noted by others before, there are still way too many choices for beginners, and even advanced users I'd say. 🤪
A '?' hyperlink to a manual chapter with some (basic) explanation may be helpful (like the one for the Cue mode in Pref -> Decks).

Not sure if it's worth the effort for 2.4.x if we drop legacy waveforms in 2.5 anyway.

[daschuer]

The mandatory part of this issue is now fixed. Do we want to close this or just remove or change the milestone?

[ronso0]

IMO polishing the list can happen anytime, so let's move it to 2.4.1 in case someone wants to take care of it.
(just don't want to dump the ideas I posted)

[acolombier]

RGB (GLSL)
RGB
RGB (legacy GL)
RGB (legacy GLSL)

Are we okay to only display the "best" rendering backend available so we can remove the (..) entirely? Perhaps list them all if --developer is passed, like for the VSyncTest?

[daschuer]

Oh, I just have noticed this is only about the appearance of each string. This has already be resolved in 2.4.0