Re: Gtk Printing and gtk_dialog_run

[Alexander Larsson <alexl redhat com>]

On Fri, 2006-04-21 at 17:33 +0200, Alexander Larsson wrote:
> On Fri, 2006-04-21 at 11:12 -0400, Matthias Clasen wrote:
> > On 4/21/06, Alexander Larsson <alexl redhat com> wrote:
> > > No, that is not the same as a finished state. The job doesn't really go
> > > into finished state until the printer has finished printing the job. If
> > > there are a lot of jobs on the printer, or if say the printer is out of
> > > paper this can take a long while. There is no need to keep the
> > > GtkPrintOperation around during this time unless you're interested in
> > > this info.
> > 
> > Ah, ok. Maybe the same as the ::end-print signal, then ? That gets emitted
> > after the last ::draw-page signal handler has returned, right ?
> 
> Yeah, except that in the future begin-print/end-print might be called
> multiple times if we use it for inline print preview.

Maybe we can just add a 
gtk_print_operation_set_report_job_progress (PrintOp *, gboolean val);

If we default it to true then the operation will go into a finished
state immediately after spooling for most people, and you only have to
call that function to get print job feedback.

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
 Alexander Larsson                                            Red Hat, Inc 
                   alexl redhat com    alla lysator liu se 
He's a genetically engineered white trash inventor who hides his scarred face 
behind a mask. She's a blind hypochondriac widow with only herself to blame. 
They fight crime!