[3.6] Project settings Audio category and subcategory incorrectly displaying / interacting.

[Lux-Ae]

Tested versions

Reproducible: Godot 3.6 Stable, 3.6 beta 5
Not reproducible: Godot 3.5.3

System information

Linux Mint 21.3

Issue description

Project Settings -> Audio category collapsible acts as button with settings, General subsection below not found in Godot 3.5.3, those are 3.6 only features, like text to speech option.

Settings remain correct and reachable, but found out because search bar navigates correctly to the "hidden" section.

Steps to reproduce

Any project should be able to access Project settings -> Audio

Minimal reproduction project (MRP)

Any project should be able to access Project settings -> Audio

[akien-mga]

Indeed 3.x and 4.x use different conventions and nesting for project settings, and this wasn't adapted when backporting TTS settings to match the old 3.x style.

[lawnjelly]

It isn't just TTS, it looks like both TTS and iOS settings are in a general tab, likely inherited from 4.x as Akien says.

The use of tabs in project settings unfortunately is a little haphazard at best (in many areas) and once committed it is difficult to change them without breaking compatibility. Although we have done in a few cases (notably rendering/2d).

In this case, it would have been easy to change if reported before 3.6 stable, as it could have been changed without breaking compatibility. This is part of why testing betas and RCs is crucial, because it provides a window where we can make such changes.

[lawnjelly]

Looking again after #98326, I didn't originally realise that some of the confusion is caused because the Audio tab itself contains settings (as well as the subfolder), whereas in most of the other folders there are no settings in the folder tab itself.

Unfortunately, there's no way around adding sub-folders and removing from the main Audio tab without majorly breaking compatibility. The only option is to move the new settings from the General tab back up to the Audio tab, but even this will break compatibility at this stage with 3.6 stable.

It could feasibly be done though (at the cost of annoying users who are using these already in 3.6 stable), we will try and discuss before 3.6.1.