> Hi,
>
> I've been going through the plugin code and there's one possibility
> I can see (although I don't know the details yet..):
>
> outputwin.cpp line 84
> if (outputBox->numLines() > 564) {
> while (outputBox->numLines() > 500)
> outputBox->removeLine(0);
> }
>
>
> Now if it turns out that every 64 lines received in the log window,
> we have the cpu hogging, then bingo.
>
> I'll look into this more.
>
> Cheers,
> Tom.
>
>
> _______________________________________________
> Licq-devel mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/licq-devel
huh.... i was just wondering about turning this into a difference of
8 lines instead of 64, which should reduce the overhead at one
certain time a little... i just changed line 84 to
if (outputBox->numLines() > 508) {
and recompiled the whole thing. let's see if the log hopping is
reduced. i noticed that sometimes the new line added to the log looks
like being smashed into the text box, which could be explained by the
64 lines being deleted at the time the line is added. i'll leave
debugging on for testing, because this fills the log a little
faster...
now i wonder how deleting 64 lines could make licq hang for about 10
seconds, even if i experienced that problem a while ago, too... but
that was with a cvs version linked to qt3, i recall. as mentioned by
jon keating, linking to qt2 should solve the problem.
regards
chris
_______________________________________________
Licq-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/licq-devel
