I wouldn't be surprised if I'm missing something here, but what is the
point of opening and closing branch insets based on whether they are
active, for every change of document setting? The attached patch removes
this behavior, which was first introduced a long time ago at fd6cd728.

To reproduce the behavior this patch changes:

1. create two new branches. Make one of them active and the other not.
Have both of them open.
2. go to Document > Settings and change a setting.

Result: the branch inset that is not activated is closed.

Even if the intention is to only do it when the user
activates/deactivates a branch in the branches tab of document settings,
I still would prefer not to assume a workflow of the user.

Thoughts?

Scott

Attachment: signature.asc
Description: PGP signature

Reply via email to