Any time I try to perform PDF export on a PDF file already openend in Acroread on Windows 7, I am getting a write error (twice) due to access limitations, then a general I/O error. While this is basically OK, it still is a nuisance: all error messages require clicking OK, then I have to close the PDF in acroread (OK, I could have done it before...), then initiate the entire process again.
Suggestion: Would it not be nice if the procedure behaves like others in Win7: if such a condition occurs, a Window pops us, saying that we cannot write on the open file, then asking us to close the file and offer the possibility to repeat the write attempt?
I would love it if it behaved that way...
reproducible with LO 188.8.131.52. (Win7 Home, 64bit)
Of course, this is a mistake by the user, but you really get the error message "Error saving the document xyz: Access to C:\...\xyz.pdf was denied." twice and afterwards in addition an error message "Error saving the document xyz: General Error. General input/output error.".
This is not logical and seems not like a feedback from a sophisticated and technically matured software.
Of course, the user has with the first error message the possibility to close the opened PDF-document and then after pressing OK of the error dialogue the pdf will be saved correctly. But this "option" is not mentioned in the dialogue.
Therefore, I would agree with the suggestion from the bug reporter. This dialogue could be improved and enhanced.
Reproducible also on my current work environment:
- Microsoft Windows 8.1, 64 bit, Ita gui, daily full updated;
- LibreOffice 184.108.40.206, win32, Ita gui and local help;
- Adobe Acrobat Reader XI, 11.0.09, win32.
I think it is a pity. The fix will save a lot of time on long documents that mean long time pdf exports.
Have a nice day,
We're replacing our use of the 'ux-advise' component with a keyword:
Component -> LibreOffice
Add Keyword: needsUXEval
Yes, a bug inherited from OO and still not fixed. It's quite annoying having to click more than necessary because the output PDF is locked.
One error message is enough, yes. Furthermore, minimizing the (modal) dialog must be permitted as well as going into the background.
(No further UX input needed at the moment.)
*** Bug 104755 has been marked as a duplicate of this bug. ***