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

List:       quanta-devel
Subject:    Re: [quanta-devel] cpu spike after closing of project properties
From:       Andras Mantia <amantia () kde ! org>
Date:       2005-08-22 20:38:35
Message-ID: 200508222338.36165.amantia () kde ! org
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


On Monday 22 August 2005 15:07, Jens Herden wrote:
> the reason is that you scan all files of the project for annotations
> after you save the project settings. Is this necessary?

Yes, because it is connected to the "newProjectLoaded" signal, emitted 
in loadProjectXML. But I'm afraid removing the signal from here and 
moving to loadProject would break too much things.

As modifying the project settings is not a commonly performed action, 
I'd suggest to keep it as it is now. In Quanta4 it will be more saner.

Andras

-- 
Quanta Plus developer - http://quanta.kdewebdev.org
K Desktop Environment - http://www.kde.org

[Attachment #5 (application/pgp-signature)]

_______________________________________________
quanta-devel mailing list
quanta-devel@kde.org
https://mail.kde.org/mailman/listinfo/quanta-devel


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