On Sun, 27 Feb 2000, Matt Koss wrote:
> On Sun, 27 Feb 2000, coolo@kde.org wrote:
> >> So the idea is to add signals to the job classes again ?
> >
> >Sure, they are the ones that know. I guess, you'll have to decide
> >which infos the slave has to provide (should be very few) and clean
> >up the slaveinterface then.
> >
> >> Any hint about where should I put the emitting of these signals ?
> >> CopyJob::slotEntries() or ?
> >
> >Depends on what you want to show I guess
>
> Well, I need almost all signals that were there :
>
> sigProcessedSize, sigProcessedFiles,
> sigTotalSize, sigTotalFiles,
> sigCanResume, sigSpeed, sigRenamed, sigCopying
>
> I guess that different jobs like CopyJob, DeleteJob etc. will emit
> different subsets of these signals, right ?

It might be worthwile to bundle these signals in a single "sigInfo" or 
so. Otherwise you need to connect a zillion signals each time you 
create a job.

Cheers,
Waldo