Moving open files

[Derek Broughton]

Kim Goldenberg wrote:

> Derek Broughton wrote:
>> Dotan Cohen wrote:
>> 
>>> Perhaps a system where the program checks to see that the file still
>>> exists, and if not, then queries the filesystem to find out what
>>> happened to it? It would be a pain to implement, I'm sure.
>> 
>> Finding out "what happened to it" is certainly a pain, but knowing that
>> the
>> file changed or moved is pretty simple.  Most KDE apps - and I would
>> expect
>> most Gnome apps - manage that much.  So they pop up a dialog that says
>> "the
>> file has moved or changed, what do you want to do?"  That should be
>> enough of a clue for all but the most clueless users :-)
> 
> Unfortunately, as has been discussed previously, OOo get around this by
> moving the file into memory and /tmp overflow files, and then rewriting
> the file when you save it, and doesn't check the existence of a file
> before writing; If it's there, you mean to replace it, if not, you are
> creating it. I'm not trying to say that OOo is correct, only that this
> was their design decision. I can come up with pros and cons on this and
> the fact is that this system does not account for the types of changes
> that occurred.

No, that makes no sense.  It was a design decision to manipulate the file in
memory and /tmp, it's got to be an oversight that they don't even check
that the original file is still there and unchanged when writing back -
it's too simple to do!
-- 
derek