TODO list for 2.0 (7/5/2001)

W. Tasin Walter.Tasin at t-online.de
Tue May 8 04:42:35 UTC 2001


Roland Krause wrote:

>--- "F at lk Brettschneider" <gigafalk at yahoo.com> wrote:
>
>>I fixed that on Sunday, already. :) KDevelop doesn't ask anymore when
>>nothing has changed outside.
>>But nevertheless, (I forgot to add it) - I noticed a new problem
>>related
>>to that: If a file was _really_ changed outside, KDevelop doesn't
>>notice
>>that. :-( This is the real number 12... ;(
>>Anyway, I can't imagine the right mechanism to solve that. Should we
>>run
>>a timer which checks all open files from minute to minute? Or should
>>we
>>check when we switch views?
>>
>
>We should check when we switch views, or when we attempt to save and
>thus would overwrite the file. But how do you check whether the file
>was changed? Is there a way to compare and save file modification time?
>
IIRC this was done by Sandy on the 1.4 branch.

IMO you should check the modification outside of the buffer ONLY if you would destroy the newer modification.... (so only on Save this file or on Save All)

Please don't do this on switching views...

Falk: The way to check it:
On loading the file to memory you should also get the time and date from the file on disk (QFileInfo I guess) and remember it (in a memory structure or similar), on file save these two values will be compared again.
If something has changed give a warning...
if not, save it and remember the new time and date from the file (again QFileInfo, never system time). 

Get always the time and date stamp from the disk (QFileInfo) and NEVER from the system time, because it can differ on remote mounted disks!!!

Ciao

Walter
-- 
  The KDevelop project: tasin at kdevelop.de - http://www.kdevelop.org
--
oohhh sveglia.... il mondo e' ammalato, ma x colpa di chi.........
(Zucchero)
:-------W. Tasin, FB 04,FHM-------------------PGP-KeyID:0x7961A645---------:
<Key-Fingerprint: 1610 835F 0080 32F4 6140  6CF7 A7D0 44CD 7961A645>
<http://wwwkeys.pgp.net:11371/pks/lookup?op=index&search=0x7961A645&fingerprint=on>




-
to unsubscribe from this list send an email to kdevelop-devel-request at kdevelop.org with the following body:
unsubscribe »your-email-address«



More information about the KDevelop-devel mailing list