The system thinks that the document has been changed by another application, perhaps another copy of Xway?
If you don’t have the document open in another copy of Xway, I’d suggest closing and reopening the document. If that doesn’t work, try quitting any applications you have open, or restart your computer.
Many thanks for your prompt reply. I’ve only the one copy of Xway on this computer so I tried your other suggestions without any luck. However, the document was located in a folder in Dropbox so I moved it back onto the iMac hard drive which seems to have worked. Odd, because I have another Xway document in Dropbox that I work on using my MacBook and Xway seems quite happy with that.
I’ll leave everything as it now, so problem solved - thanks for your help.
Dropbox could well have ‘touched’ the file as a part of its normal
operation; (to ‘touch’ being a Unix term) and Xway could have seen that
‘touch’ as a modification even though no data was changed.
The autosave shenanigans is mostly all handled in the system so I’m uncertain what exactly constitutes a change that will get in the way of autosave. It’s certainly plausible that touching, especially if it alters the modified date, could cause it.
Have you been using Xway on multiple computers through DropBox? If so, could the document have been opened before DropBox had finished syncing?
I have Xway on two computers but the document in question was newly created on the iMac and had not been opened on the MacBook. Xway was not open on the MacBook at the time. The problem seemed to be confined to the one document on the iMac as other Xway documents on the MacBook have always been ok.
As I said, taking the document out of Dropbox seems to have solved the issue so that’s where it’ll be staying!