This is exaclty what I meant, Paul!
I completely agree with you!
Carlo
ing. Carlo Strata
-
via Botticelli 1/4
30031 Dolo - VE
Italia - Italy
-
tel. +39.041.822.0665
cell. +39.347.85.69.824
Skype carlo.strata
Google carlo.strata.69
-
carlo.str...@tiscali.it
PEC: carlo.str...@ingpec.eu
Il 30/11/2014 14:43, Paul ha scritto:
As I understand it, the OP isn't complaining about the fact that the
file is locked, rather, about the fact that LO spends (potentially a
lot of) time processing the file before reporting the problem.
Instead, LO could check access to the file early, and report the problem
before wasting time processing. For the most common use cases, this
would save the user some time. That is something that *does* belong to
LO.
Of course, there would still be edge cases where the file wasn't locked
when LO started processing the pdf, but became locked by the time LO
finished. There is nothing that can be done about that, short of LO
itself locking the file, which may or may not be desired.
Paul
On Sun, 30 Nov 2014 13:55:37 +0100
Jaroslaw Staniek <stan...@kde.org> wrote:
Hi,
Google for "acrobat reader file locking" and you'd notice that this
unnecessary locking is inherent issue of Windows. You're dealing with
behavior largely inherited from the MS DOS era. You can pick other pdf
reader. Or publish to a web server and open the file using web browser
-it's lockless.
If you ask about Linux, it was solved *properly* years ago. If you're
a pro you can try e.g. Okular reader which reloads the pdf
automatically and never locks. Why would it in a modern multiuser
Inernet-enabled environment?
The bug doesn't belong to LO. Error message can be added, but IMHO
just to annoy users in a different way...
On Sunday, 30 November 2014, Carlo Strata <carlo.str...@tiscali.it>
wrote:
Hi Everyone,
I see that an exact issue already exists since 08/2012!!!
https://bugs.freedesktop.org/show_bug.cgi?id=53530
I think it could be a user time saving big fix and it could be a
very
appreciated update/fix in professional job/activities too.
I also currently don't know if the same behaviour happen on other
environment like linux and/or MacOS X.
I think the pdf file state could be test other than the mere
existence,
couldn't it?
Have a nice Sunday,
Carlo
--
ing. Carlo Strata
-
via Botticelli 1/4
30031 Dolo - VE
Italia - Italy
-
tel. +39.041.822.0665
cell. +39.347.85.69.824
Skype carlo.strata
Google carlo.strata.69
-
carlo.str...@tiscali.it
PEC: carlo.str...@ingpec.eu
Il 29/11/2014 13:27, Carlo Strata ha scritto:
Hi Everyone,
I use LibreOffice for all my job activities and I yield many pdf
documents. Many time I change the original document and update the
associate pdf. If I forget (!) to close the pdf document on my viewer
(see below), not necessarily the viewer itself, I get a nice sequence
of "I/O errors" and the export operation obviously fails!
If I export a long document I have to repeat the long time
operation and
to waste my time.
So, why not check whether the file is locked (opened) by another
program
before (!) starting exporting over it? I think it is possible.
Wht do you think about? Is there already an issue about this
behaviour?
My current work environment is:
- Microsoft Windows 8.1, 64 bit, Ita gui, daily full updated;
- LibreOffice 4.3.5.1, win32, Ita gui and local help;
- Adobe Acrobat Reader XI, 11.0.09, win32.
Have All a nice weekend,
Carlo
--
To unsubscribe e-mail to: users+unsubscr...@global.libreoffice.org
Problems?
http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more:
http://wiki.documentfoundation.org/Netiquette List archive:
http://listarchives.libreoffice.org/global/users/ All messages sent
to this list will be publicly archived and cannot be
deleted
--
To unsubscribe e-mail to: users+unsubscr...@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted
