This was decided on by the material & process engineers. It's a pretty safe change since the support brim pretty much has only advantages if there is no support infill.
Fixes ST-3552.
These have moved. The Support Structure setting was already present in the support category.
Done as a 5 minute fix while working on the Settings Guide.
I think for the support meshes, some settings were simply missed because they are in completely different categories. For instance, the support flow rate also applies to support meshes so those settings should be visible.
For the tree support settings, I think that when the tree support became activated by support_structure, the developer checked for instances where the support_tree_enable setting made a setting visible (as alternative to the normal support_enable setting). Like Support Infill Density used to be visible if normal support or tree support was enabled, and now needs to check only for normal support. However they didn't also look for settings that are ONLY available for normal support and not for tree support. So those settings now have extra conditions that disable them if the support structure is set to tree support.
With this I tried to word the check correctly in case we ever get a third support construction type. Like, sometimes a setting is not shown with tree support because tree support explicitly doesn't support it (e.g. Conical Support), but sometimes it's not shown with tree support because it's specific to area support (e.g. support join distance).
Done as a five minute fix (although typing this commit message also took five minutes) as I encountered these problems while working on the settings guide.
That was still missing, oops. I'm aborting the translations to get this in. It's important enough to break the string freeze and restart the translations process at this stage.
Contributes to issue CURA-7622.
Some printers stylize themselves with allcaps to gain more attention or because they use fonts that don't have lowercase (especially Asian brands) or to mix it with fixed-width characters. Here we'd like to keep them all equal, so they get proper name-style capitalisation.
As discussed in the CCB this morning. Since the new profile will be the _changed to_ profile rather than the _changed from_ (the latter of which would make the button useful, but since the profile is already switched at that point it would be a lot of work), the 'Create New Profile ...' button (in the Keep/Discard dialog) is redundant, since you can always create a new profile if you select keep changes.
