------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.kde.org/show_bug.cgi?id=154960
------- Additional Comments From Thomas.McGuire gmx net 2008-01-06 21:09
-------
I don't know much about the job classes myself.
Here are some observations. As I don't have IMAP myself, I can not test
anything. Maybe you can put together the pieces.
1.
KCompositeJob already has a slotInfoMessage function, which is even virtual.
These could mean that the slotInfoMessage in QuotaJob is supposed to override
that. Also, the signature of slotInfoMessage changed: Before, it was in another
class (in jobclasses.h) and had only two arguments, now it is in KCompositeJob
(which is new) and has an additional argument
http://websvn.kde.org/?view=rev&revision=558448
http://api.kde.org/4.0-api/kdelibs-apidocs/kdecore/html/classKCompositeJob.html
2.
In the enterprise branch, which probably works correctly, there is also no
emitResult.
See
http://websvn.kde.org/branches/kdepim/enterprise/kdepim/kmail/quotajobs.cpp?revision=631694&view=markup
>Does anyone know more about the KIO::Job class to tell me if you need to call
>the emitResult() function manually, or does this class somehow trigger this
>automatically?
Till told me it is emitted automatically. You can probably place a breakpoint
in slotQuotaResult of kmfoldercachedimap and find out when it is emitted (using
the 3.5 or enterprise branch).
I think (but I might be wrong) that slotInfoMessage is supposed to be called
automatically whenever a subjob emits the infoMessage signal. See the code for
KCompositeJob::addSubjob, which does that. That would explain why it doesn't
work in QuotaJob, since that wasn't adopted to the new slotInfoMessage
signature.
I do wonder why a connect for infoMessage/slotInfoMessage is done in QuotaJob
at all then...
Generally I suggest using GDB to debug the problem. Place a breakpoint in
slotInfoMessage and see if it is called at all. If not, find out why...
_______________________________________________
Kdepim-bugs mailing list
[email protected]
https://mail.kde.org/mailman/listinfo/kdepim-bugs
