autosave
Kris Wong
wongk at seapine.com
Wed Apr 4 12:52:25 UTC 2007
> Here's a quick stab at autosave for KDevelop3.
>
> The implementation is straightforward and the only curious thing is
probably
> the m_isSaving flag. It's needed to weed out a corner case where if a
file
> has been externally modified and the autosave kicks in, KDevelop will
show a
> messagebox asking the user for confirmation. Without this flag to keep
track
> of this state, the messagebox will be launched again and again (for
every
> autosave) and this is potentially really bad.
>
> I put the configuration in Settings -> Configure KDevelop -> Editor.
>
> Opinions? Worth applying?
W/o having applied the patch yet, I can think of a few times when I
wished KDevelop had this feature. Seems fairly isolated, not much
chance of a regression. It get's my vote. =]
Kris Wong
More information about the KDevelop-devel
mailing list