[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-22 12:07:56
Message-ID: 200508221908.02069.jens () kdewebdev ! org
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


Hi Andras,

> > > when I have a project in Quanta and change the project settings I get
> > > a unusual load of 100% at the system for a couple of seconds after
> > > Quanta wrote the project settings to disk.
> > > Quanta is doing something but what???
> > > This happens every time I change some settings in the dialog and save
> > > them.
> >
> > Writing out the XML and loading again?
>
> no impossible, because Quanta 3.4 does not have it.

the reason is that you scan all files of the project for annotations after you 
save the project settings. Is this necessary?

Some more questions to this:

You read the files line by line but limit the line length to 2000, why? AFAIK 
does the next read continue where the previous stopped. In case you have a 
line longer than 2000 character you would mix up your line counting.

What is the meaning of the syntax with the round brackets? If I write 
something like "@annotation(" I get nothing behind the opening bracket. Is 
this wanted? And do you really need the ':' behind the closing bracket?

The scan of the files only scans one line, so that something like 

	<!-- @annotation
		this is my first annotation
	-->

would display nothing. Is this wanted?

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]