Gregory Jefferis writes:
> It turns out that BufferList::setCurrentAuthor is not really the issue.
> Rather it is because the default constructor for Changes includes an
> authorid of 0, therefore assuming that the relevant author list has the
> current author at position 0. There is no way for t
Dear Gregory,
>>> 1) Would it be possible to stop this resorting of the author
>>> list from happening? Perhaps by recording the current author
>>> id in the AuthorList rather than insisting that it must be 0
>I think that the answer to my own question is that internally
>the current author mu
Dear José,
Thanks for your response.
On 2009-05-18 18:06, "José Matos" wrote:
> On Wednesday 13 May 2009 17:25:53 Gregory Jefferis wrote:
>> BufferList::setCurrentAuthor
>>
>> Insisting that the current author have id 0.
It turns out that BufferList::setCurrentAuthor is not really the issue.
> I have noticed that the when current LyX (1.6.2) reads and writes a
> document containing multiple authors for tracked changes it re-orders
> the Author List. For example if Andy and Bert are both working on a
> document, when Andy saves, he will be author 0. If Bert then loads
> the file ad
On Wednesday 13 May 2009 17:25:53 Gregory Jefferis wrote:
> Dear LyX developers (especially John Levon & Lars Gullik Bjønnes I think),
>
> I have noticed that the when current LyX (1.6.2) reads and writes a
> document containing multiple authors for tracked changes it re-orders the
> Author List. F
