Paul wrote:
I also read the issue that has been lodged and therefore understand
the arguments. However from my perspective it should save a version on
closing, even if the document is saved as well - ie, save, then close
- version saved.
Yes, there are good arguments on both sides. This
Am Montag, 23. Mai 2005 22:53 schrieb Mathias Bauer:
Klaus Schneider wrote:
Paul wrote:
I've been trying out the version control in 1.9.95 (on winxp) but I
think the 'save new version on closing' is not working. I want to get
someone else to try it out prior to submitting a bug for it.
I also read the issue that has been lodged and therefore understand
the arguments. However from my perspective it should save a version on
closing, even if the document is saved as well - ie, save, then close
- version saved.
This, for me, is used to track what has changed in a document over
Paul wrote:
I've been trying out the version control in 1.9.95 (on winxp) but I
think the 'save new version on closing' is not working. I want to get
someone else to try it out prior to submitting a bug for it.
Basically under file versions (using a file in the .odt format in
writer) I select
Klaus Schneider wrote:
Paul wrote:
I've been trying out the version control in 1.9.95 (on winxp) but I
think the 'save new version on closing' is not working. I want to get
someone else to try it out prior to submitting a bug for it.
Basically under file versions (using a file in the .odt
I've been trying out the version control in 1.9.95 (on winxp) but I
think the 'save new version on closing' is not working. I want to get
someone else to try it out prior to submitting a bug for it.
Basically under file versions (using a file in the .odt format in
writer) I select the check box
You are using an old version. The new version is 1.9.104
Paul wrote:
I've been trying out the version control in 1.9.95 (on winxp) but I
think the 'save new version on closing' is not working. I want to get
someone else to try it out prior to submitting a bug for it.
Basically under file
who has got a later dev build to give it a go and see
I fully realised that the version I have is not the latest and the
purpose of the email was to see if someone who was using a later build
to try this potential bug out.
There is no point in me downloading 80Mb of file to test out this
single
