Hi folks, I would like to inform you about two issues that I am going to address this evening. If you disagree, please complain loudly. Otherwise, I will continue the CT cleanup...
1. Change time Every change has a time. This time is used as a guidance for the user while editing his document. It is completely irrelevant for LaTeX export. Presently, each new change gets time 0 (zero). However, when you save your document, the time is substituted by the current time (i.e. the time of saving). This "semi-session-like" time management is unfortunate for several reasons: First, the change times depend on when and how often you save your documents. If you edit a file, (auto-)save it, and continue editing, you will definitely get two distinct changes. Moreover, the change time is only displayed after file saving. I am going to change LyX's behaviour such that change times always reflect the exact time at which the change took place. This is in line with OO and MS Word. To avoid that every keystroke results in a separate change, I will also introduce a tolerance interval of, say 5 minutes. That means if there are two adjacent changes that only differ in their change time with delta < 5min, they will be merged (and the later change time is preserved). 2. Cleverer reject-changes Presently, if you delete an inset, all its content is deleted recursively. This is unfortunate. Imagine that your colleague makes changes in an existing inset. He sends it to you and you come to the conclusion that the inset should go completely. If you erase it, LyX will delete all text within the inset, i.e., the CT'ed insertions of your colleague are lost and there is no way to reanimate them later. I am going to change this behaviour in a way that the inset's content remains untouched if you delete the inset. Moreover, reject-Changes will not reject changes in nested insets unless the inset itself is set to UNCHANGED. What sounds like extra work in fact leads to less code, because I can remove several methods at the same time. I hope this makes sense to you. CT is getting better and simpler every day :-) Regards, Michael
