Quote:
Originally Posted by Arkadian
Indeed... but have you got any suggestion as to what might cause it?
|
No.
But I did make some suggestions as to how I would go about finding out what was happening - did you try any of them ?
Quote:
Originally Posted by Arkadian
I must be doing something that it is triggering it.
|
Indeed, but I can't see what you're actually doing - so I have to try to imagine what you are doing
One scenario I suggested was that when you Save the book, you're not saving it where you think you're saving it and I suggested you search for it.
If you initiate the save with ctrl/s or click the Save button and for some reason the editor doesn't have at least one file marked as changed. then nothing happens. In that case
File->Save will be disabled (grey), however, a ctrl/s or a click on the save button will do nothing; you get no 'nothing to save' warning, but nor would you get any such warning in any other programs I can think of.
Actually the save button is greyed out, but on my rig with my eyes that's hard to discern with the 'standard' icon, so I override the grey snail (save.png) with a blue diskette, it makes it more obvious because the blue becomes grey when there are no changed files.
I prefer to use Save As (in all programs), its explicit, I can knowingly save over something and consciously say Yes to overwrite it, then if anything goes wrong I know I did it. And it gives me a primitive version control ability using my filename.number.ext convention.
Another scenario is that you may be inadvertently initiating the
Edit->Revert to initial state feature.
BR