[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:       Jens Herden <jens () kdewebdev ! org>
Date:       2005-08-23 15:43:04
Message-ID: 200508232243.11011.jens () kdewebdev ! org
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


Andras,

> Read my other mail. 

I did, but after I wrote the other mail.

> Do you think it is worth to introduce a new signal? 

Yes, I think so. It is better than scanning again.
BTW You changed the timer for the file scanning to 200 but this is very slow 
now. My CPU is almost loadfree and the harddisk led is blinking but it takes 
ages until the annotations are updated. 


> I'm wondering why I did not use QTextStream here to read like in other
> places.... Try it now.

Works fine now!

> > I see. So you do not need the ':', right?
>
> If it's in one line, it might be important. Do you think we should not
> have it?

I don't get this. What is it important for? And I see not difference if you 
look for '):' or ')'


I fixed the parser problem too. You could not see it because it was only 
visible if you do not autoload the files on startup of Quanta.
During debug I got the impression that some timers are working during the 
startup phase of Quanta. Like the special area timer. 

Jens

[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]