edw3cats

Many of you probably already noticed it. I felt strangely happy when I saw it, congrats.

Thanks @Carl123, that's really good to know.

Thanks for your reply, I see the reason now, but a problem is a problem, for people exporting hundreds of files and long hours it gets a bit annoying sometimes, even when I have all the keyboard shortcuts memorized. Working around this history concept of history, maybe a default exception list to what is marked as modified, that will help smooth out this kind of minor usability issues, and will only make the program better. That is the reason for my post, to help them help users like me. Also note that that is my only complaint about the whole export process, everything else is fine. I do not demand that they address it now, but only to take note, and perhaps drop it into a to do list for one of their developer teams who handles usability. Another option is to come up with a batch processing feature, perhaps for a future version or even in the 2.0 branch.

Steps to reproduce: - Open an image - File > Export to a different format (not sure about same format) - Export action marks document as [modified] - Close document. This prompts user asking to save the modified document, but document was never modified. The problem is that extra step of clicking no or typing N key every time when the document was not modified.