Policy change: hiding a group should not affect its enablement
* in the past, the default behavior was: hiding a group would disable it, and then showing the group would re-enable it * problem occurs when user has disabled a group; hiding and showing it unexpectedly re-enable the group * there was a config variable to disable this behavior, but it was never shown on the GUI and therefore not discoverable Despite the longstanding policy, there's really no reason for group visibility and enablement to be intertwined. If this chnage causes a big problem for someone, they can revert to the prior behavior by setting the new config variable in the text file
This commit is contained in:
parent
70251c758d
commit
3b49422277
@ -196,7 +196,7 @@ CONFIG_VARIABLE (bool, copy_demo_sessions, "copy-demo-sessions", true)
|
||||
CONFIG_VARIABLE (std::string, auditioner_output_left, "auditioner-output-left", "default")
|
||||
CONFIG_VARIABLE (std::string, auditioner_output_right, "auditioner-output-right", "default")
|
||||
CONFIG_VARIABLE (bool, replicate_missing_region_channels, "replicate-missing-region-channels", true)
|
||||
CONFIG_VARIABLE (bool, hiding_groups_deactivates_groups, "hiding-groups-deactivates-groups", true)
|
||||
CONFIG_VARIABLE (bool, hiding_groups_deactivates_groups, "deprecated-hiding-groups-deactivates-groups", false) /*deprecated*/
|
||||
CONFIG_VARIABLE (bool, group_override_inverts, "group-override-inverts", true)
|
||||
CONFIG_VARIABLE (bool, verify_remove_last_capture, "verify-remove-last-capture", true)
|
||||
CONFIG_VARIABLE (bool, save_history, "save-history", true)
|
||||
|
Loading…
Reference in New Issue
Block a user