On Tue, May 09, 2006 at 10:52:27PM +0200, Michael Gerz wrote: > >> case LFUN_CHANGE_REJECT: // what about these two > >> case LFUN_ALL_CHANGES_ACCEPT: > >> case LFUN_ALL_CHANGES_REJECT: > >>- flag.enabled(buffer_ && buffer_->params().tracking_changes); > >>+ flag.enabled(buffer_); > >> > >> > > > >Will there be a plan to re-enable the test at some point? I.E. are you > >going to make "there are unaccepted changes" an O(1) operation on the > >buffer? > > > > > No. The test has been removed on purpose. In fact, the major motivation > of the CT code changes is the user requirement to switch CT off without > having to accept all changes before.
I know. Read what I wrote :) These should be disabled if there's nothing /to/ reject or accept. If that's too hard or slow to do then OK, but we should try. > Change tracking and change output can be enable/disabled. The current > status is indicated in the LyX menu. More specific please. regards, john
