Need help with testing asynchronous saving branch! :)

[Dmitry Kazakov]

Hi, Alvin!

Thank you very much for your testing. I actually forgot about this flag, 
so it saved the mergedimage as well.

I have fixed it, and now it shouldn't save the stuff anymore:
https://commits.kde.org/krita/27a9873aba0be3816a406027ab8d3ac298a884e7



On 28.07.2017 20:53, Alvin Wong wrote:
> Hi Dmitry,
>
> I've tested it for a short while on Windows with the python branch
> merged in (so using Qt 5.9.1) with multiple files opened and the
> autosave seems to work nicely, saving works, no crashes or lockups.
>
> It's not a lot of in-depth testing but my impression is pretty good!
>
> One thing I noticed is that the autosaved file contains
> `mergedimage.png` and `preview.png`. Autosaves on 3.2 beta 2 seems to
> only saves `preview.png` (and I seem to remember earlier versions
> (probably during the 3.0 times) not even having `preview.png`). Would
> it cause undesirable overhead during autosaving or is it intended?
>
> Best Regards,
>
> Alvin Wong
>
> 2017-07-27 23:26 GMT+08:00 Dmitry Kazakov <dimula73 at gmail.com>:
>> Hi, all!
>>
>> I have fixed all your previous reports! Please test the branch again! If no
>> severe regressions found, I will merge it to master :)
>>
>> To test do:
>>
>> git checkout kazakov/async-saving
>>
>> and build as usual :)
>>
>>
>> The issues can be tracked here:
>> https://phabricator.kde.org/T6542
>>
>>
>>
>>
>> --
>> Dmitry Kazakov

-- 
Dmitry Kazakov

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kimageshop/attachments/20170729/fa31cbea/attachment.html>