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

List:       kde-commits
Subject:    Re: KDE/kdelibs/kdecore/jobs (silent)
From:       Ramon Zarazua <rzarazua () digipen ! edu>
Date:       2009-06-29 20:15:03
Message-ID: 200906292215.25687.rzarazua () digipen ! edu
[Download RAW message or body]


On Monday 29 June 2009 07:54:27 am Kevin Ottens wrote:
> On Sunday 28 June 2009 16:36:33 David Faure wrote:
> > On Sunday 28 June 2009, Ramon Zarazua wrote:
> > > -     * @note: Deletes this job using deleteLater().
> > > +     * @note: Deletes this job using deleteLater(), this function will
> > > NOT return from +     *        your worker method.
> > >       *
> >
> > What do you mean by worker method? And by "not return" ??
> > Surely emitResult() returns. I don't understand this docu change.
>
> Hmm, it indeed makes no sense to me. The other bit of change (swapping
> "delete" for "suicide") seems also wrong.
>
> I'd propose to just revert this commit if we don't get some explanation
> about the intent of it.
>
> Regards.

Well here is the experience I had: What I gathered from the documentation is 
that start should call another worker method through the event loop. I tried 
calling it with QTimer::singleShot, however I could not get it to work. For 
testing purposes I decided to call the worker method inside of start().

Afterwards I realized that emitResult() was not instantly suiciding the job as 
I was led to believe. I asked around a bit on kde-devel(mentioning that I 
could not get it to be called through the event loop), and I was told that it 
doesn't matter, and that return should be called. If I was misinformed I 
apologize in advance, however that means that documentation is still not 
completely clear.
--
Ramon Zarazua
Bachelor of Science in Real Time Interactive Simulation
at
Digipen Institute of technology

["signature.asc" (application/pgp-signature)]

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