Moving open files

[Dotan Cohen]

2008/7/7 Derek Broughton <news at pointerstop.ca>:
> Dotan Cohen wrote:
>
>> 2008/7/7 Derek Broughton <news at pointerstop.ca>:
>>> It can't be KDE's, because OO isn't a KDE app.
>>>
>>
>> KDE's Dolphin was used to move the file, I should have been clearer.
>
> That doesn't matter though.  It's up to the application to handle the
> (re)moving of a file safely.
>>
>>> What, exactly, is the loss?
>>
>> The original file (in the new location) does not contain the changes.
>> You could argue that the changes remain in the old location, but the
>> user does not know to even look there. For him, the data is lost.
> ...
>> As Carl-Mitchell mentioned, OOo should have locked the file. I am
>> unfamiliar with file locks, but now that I know about the problem I
>> will try to reproduce it locally and file a bug at OOo.
>
> No, sorry, I don't agree with that.  You may not like the behaviour, but it
> is logical.  Would you still think it's a bug if the user had just _copied_
> the original, and then there were two different versions?  I can't do
> exactly the same thing with Word, because it _does_ lock the file, but
> that's a design choice.

In my opinion, and the opinion of he who 'lost' his data, there should
be a lock file.

> By all means, file a bug report, but I wouldn't be terribly surprised if
> they won't consider it.  Of course, if nobody files a bug report, they
> _definitely_ won't consider it :-)

Thanks, I will file it. Maybe it could be optional.

Dotan Cohen

http://what-is-what.com
http://gibberish.co.il
א-ב-ג-ד-ה-ו-ז-ח-ט-י-ך-כ-ל-ם-מ-ן-נ-ס-ע-ף-פ-ץ-צ-ק-ר-ש-ת

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?