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

List:       kde-devel
Subject:    Re: Print error report (RFC)
From:       Michael Goffioul <goffioul () imec ! be>
Date:       2001-03-31 10:40:14
[Download RAW message or body]

> I rather would go for int failed() with a numerical error code and 0 = OK.
> (In addition to failReason())

The errors I consider here, are the errors generated inside the plugin while
printing the PS generated by Qt. This doesn't include the Qt drawings error.
And the error generated is (almost) completely dependent on the plugin itself.
Of course you can still find some similar errors in various plugins, but for
example there won't be any common error between the CUPS plugin and the
RLPR plugin.
So my idea was to simply to tell the application something went wrong using
"bool failed()", and then the application can use "QString failReason()" to
have more informations. The error message itself is determined in the plugin.
So is it really necessary to report some kind of enum value (error code) as:
    - the error will be reported using KNotify anyway
    - as the error occured in the plugin, the application won't be able to correct
        it itself. The error will be "structural" (like missing program, network error,
        daemon crash, wrong printer configuration, printer unknown).

Michael.

--
------------------------------------------------------------------
Michael Goffioul                IMEC-DESICS-MIRA
e-mail: goffioul@imec.be        (Mixed-Signal and RF Applications)
Tel:    +32/16/28-8510          Kapeldreef, 75
Fax:    +32/16/28-1515          3001 HEVERLEE, BELGIUM
------------------------------------------------------------------



 
>> Visit http://master.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

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