Export marks document as changed

[DarkClown]

I was wondering if there is any need for a document being marked as "changed" after exporting the document?
When I save my document, export afterwards and want to close it I get asked if I want to save the changes - what comes across as an unnecessary question since the export does not change anything in the before alredy saved document - but it just adds another user action to close the document. This may not seem important when working with a single document - but when processing plenty of files this can be seriously  annoying.

[Dan C]

Hi @DarkClown,

This has been raised on the Forum previously, with information as to why the document is marked as 'Modified' here - 

Interestingly, when searching the forums for a previous post regarding this, I actually found a post from yourself in 2020, asking the same question!

I hope this clears things up

[DarkClown]

Hmm, that's 3/5 years in the past. We are now on AP 2.11 ... 🙂

And seeing that of course the export is mentioned in the history (why?) considering I did not change any export setting. I still don't see any need to save changes I did not make anywhere.

So I guees it's still not a bug but a feature

[MikeTO]

There's one other change that's made in the file when you print or export - it updates the last printed/exported date/time in the metadata. That can be viewed with Publisher's Fields panel.

The alternative would be to automatically save the file after printing or exporting and I don't think most of us would want that.

[thomaso]

13 hours ago, MikeTO said:

There's one other change that's made in the file when you print or export - it updates the last printed/exported date/time in the metadata. That can be viewed with Publisher's Fields panel.

Does this Date field entry in V2 indeed trigger a "modified" state + turn the "Save" command from grayed-out to selectable?

I am asking because to me in V1 it does not, with or without "Time" activated additionally for this field. Although I see the time entry changing after an export, the modified state doesn't change and no History entry gets added. To me only those actions cause a "modified" state that also cause an History entry, like e.g. selecting a layer or just making a different page "active".

[Pšenda]

15 hours ago, MikeTO said:

it updates the last printed/exported date/time in the metadata

...

 

[MikeTO]

1 hour ago, thomaso said:

Does this Date field entry in V2 indeed trigger a "modified" state + turn the "Save" command from grayed-out to selectable?

I am asking because to me in V1 it does not, with or without "Time" activated additionally for this field. Although I see the time entry changing after an export, the modified state doesn't change and no History entry gets added. To me only those actions cause a "modified" state that also cause an History entry, like e.g. selecting a layer or just making a different page "active".

In v2 on macOS, if the last printed/exported field is set date only, and you printed or exported it today, then printing and exporting will not mark the document as modified. But if it's set to time or date and time, then printing and exporting will mark the document as modified.

Mike