On Sat, Jan 21, 2017 at 11:32:27PM -0500, Scott Kostyshak wrote:
> On Mon, Nov 21, 2016 at 09:34:40PM -0500, Scott Kostyshak wrote:
> > On Tue, Nov 22, 2016 at 09:07:35AM +1300, Andrew Parsloe wrote:
> > > On 21/11/2016 6:34 p.m., Scott Kostyshak wrote:
> > 
> > > As an occasional user of branches, when I deactivate a branch I expect the
> > > state of insets in the branch to be left in their current state, some 
> > > open,
> > > some closed, as the case may be. When I reactivate the branch I expect to
> > > recover that previous state. This seems to me the *minimal* assumption for
> > > LyX to make -- there was, presumably, good reason for the insets to be in
> > > that particular configuration. LyX should respect that when the branch is
> > > reactivated.
> > 
> > Thanks for the feedback, Günter and Andrew. I propose two questions for
> > going forward:
> > 
> > (1) Do others agree that LyX should be consistent and treat
> > activating/deactivating branches from right-clicking on a branch inset
> > the same as activating from Document Settings?
> > 
> > (2) Which behavior should be changed?
> > 
> > If the answer to (1) is "it is not inconsistent to treat those
> > situations differently", then we can just leave things as they are and
> > we don't need to change anything. If the answer is that we should change
> > one or the other to be consistent, then we need to debate (2).
> > 
> > For (2), the code for document settings explicitly makes a point to
> > open/close the activated/deactivated branches, and it has been this way
> > for a very long time, from what I see. So the burden would be on us to
> > argue that changing it makes considerably more sense than changing the
> > right-click activate/deactivate. I'm not sure how to proceed in this
> > case. If other developers agree, we could ask on lyx-users to see what
> > they think. I think this is a perfect situation for taking a poll of
> > users.
> 
> I'm still looking for feedback on the above issue.

If no one has feedback, I'll make a decision and commit to master.

Scott

Attachment: signature.asc
Description: PGP signature

Reply via email to