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

List:       kde-bugs-dist
Subject:    [Bug 70630] Better file cleanup or tidying
From:       Sean Clarke <sean.e.clarke () ntlworld ! com>
Date:       2004-01-16 18:32:02
Message-ID: 20040116183202.10640.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
      
http://bugs.kde.org/show_bug.cgi?id=70630      




------- Additional Comments From sean.e.clarke@ntlworld.com  2004-01-16 19:32 -------
Hmm.. I've implemented it differently (perhaps that's why it was easy?)

I've added a new option to the KileConfigDialog, under the "Reopen files and projects \
on startup." called something like "Clean temp files on document/project close". This \
sets a new option in the KConfig object under "Files", "AutoCleanUp" etc.

Then in Kile::fileClose() I check to see if this file is part of a project, if not I \
call the Kile::CleanAll()... you are right, presently I get the confirmation dialog \
box (hey it is WIP :-) ), what I was going to do is pass a parameter into CleanAll \
that determines if the dialog box is displayed. The default would be true, but when I \
"auto" tidy up it would be false and hence no dialog appears.

Note with this method even when the user is not asked what files to delete it still \
uses the same list of file extensions, so I could implement a user selectable list \
(series of checkboxes? or other QT widget) and that would set the CleanUp \
configuration for both the file close and manual clean up.

I thought about KileDocumentInfo, but thought the "Automatic cleanup" was a kile \
configuration rather than document configuration issue.

Is this not acceptable/incorrect?


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