[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kdevelop-devel
Subject:    Re: TODO list for 2.0 (7/5/2001)
From:       "F () lk Brettschneider" <gigafalk () yahoo ! com>
Date:       2001-05-08 6:14:37
[Download RAW message or body]

Jens Zurheide wrote:
> 
> Tuesday 08 May 2001 06:42 W. Tasin
> > Roland Krause wrote:
> > > --- "F@lk Brettschneider" <gigafalk@yahoo.com> wrote:
> > > 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).
> > 
> I would favour if the check is performed on changing the views and maybe even
> on editing. What if a file really changes outside the editor and you do not
> notice it, you start changing it in the editor and finally you want to save
> it? You will most probably loose time. (The time for comparing two timestamps
> against each other should not be the problem.)
Well, thanks a lot for the hints mates, my today's decision would be to
implement it like in MS Visual C++ 6.0. MSVC takes a check for all open
files whenever the mainframe window has got a focusIn event. And I think
that is the best way. You change a file outside KDevelop and after that
you switch back to KDevelop where it will be noticed _immediately_. And
it means to avoid unnecessary checks. What do you think about this
suggestion?

BTW: Hmm...In Toplevel MDI mode, it is necessary to check the open files
with every focusIn event of any toplevel view. Additionally, we could
use DocViewMan::slot_gotFocus as central point.

Cheers,
F@lk

_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com


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


[prev in list] [next in list] [prev in thread] [next in thread]