Jean-Marc Lasgouttes wrote:
michael> Presently, if you delete an inset, all its content is deleted
michael> recursively. This is unfortunate. Imagine that your colleague
michael> makes changes in an existing inset. He sends it to you and
michael> you come to the conclusion that the inset should go
michael> completely. If you erase it, LyX will delete all text within
michael> the inset, i.e., the CT'ed insertions of your colleague are
michael> lost and there is no way to reanimate them later. I am going
michael> to change this behaviour in a way that the inset's content
michael> remains untouched if you delete the inset. Moreover,
michael> reject-Changes will not reject changes in nested insets
michael> unless the inset itself is set to UNCHANGED. What sounds like
michael> extra work in fact leads to less code, because I can remove
michael> several methods at the same time.
But currently, one can delete an INSERTED change even if it is done by
someone else, I think. We need a global solution.
Both improvements have been committed. Man, coding has become a real joy!
Michael
