https://bugs.kde.org/show_bug.cgi?id=291374
--- Comment #16 from Sebastian Sauer ---
Created attachment 69347
--> https://bugs.kde.org/attachment.cgi?id=69347&action=edit
Patch for KSaveFile that maybe fixes the issue
re KSaveFile; the current code and with it the bug is gone w
https://bugs.kde.org/show_bug.cgi?id=291374
--- Comment #13 from Sebastian Sauer ---
If my assumption above is true then just creating any QTemporaryFile zip-file
using KArchive would always fail. It should be rather easy to make a simple
test-case but since I do not have a KDE windows devel
https://bugs.kde.org/show_bug.cgi?id=291374
--- Comment #12 from Sebastian Sauer ---
Suggestion would be to not use KSaveFile in KArchive. Just create the archive
and check later or on write if writing/saving it failed
--
You are receiving this mail because:
You are on the CC list for the
https://bugs.kde.org/show_bug.cgi?id=291374
--- Comment #11 from Sebastian Sauer ---
There btw is a
bool QTemporaryFileEngine::rename(const QString &newName)
{
QFSFileEngine::close();
return QFSFileEngine::rename(newName);
}
which does really close the temporary-file using
https://bugs.kde.org/show_bug.cgi?id=291374
--- Comment #10 from Sebastian Sauer ---
I think the reason could be that the temporary file is still open. Windows
cannot rename files that are opened at least afaik. The problem is that
KTemporaryFile/QTemporaryFile::close() does *NOT* close the
file
https://bugs.kde.org/show_bug.cgi?id=210098
Sebastian Sauer changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
CC
