[scribus] Save Not Setting Saved Status

[Gregory Pittman]

On 06/14/2011 06:45 AM, JLuc wrote:
> Le 14/06/2011 11:54, Craig Bradney a écrit :
>
>> Its easy to locate where the flag gets changed but there are a million
>> and one places it can be called...
>
> Then, why not go for one million and TWO ?
>
The danger has been, I think, that a brute force 'fix' might fail to 
warn you about changes you have made as you try to exit Scribus.

This seems to be the case with Scripter, when you set the docChanged() 
flag -- it doesn't seem to work, and you can easily lose your changes if 
you don't know this.

Greg