|
|
On 2020-04-21 10:24, 'Phil' via fltk.general wrote:
> Thanks Manolo, now I've been there it'll be the first thing I check.
I suppose in your app you can pop a dialog warning of the various
possible causes of errors you notice that can be the problem,
and to have the user check the printer log on that platform,
as I imagine errors from the print system end up in a log somewhere,
e.g. on linux the /var/log/cups, on windows I don't know the Event Viewer?
Depending on how verbose you want to get, you can either recommend or
automatically open the printer error log. I think on windows you can
open the event viewer with e.g. system("eventvwr"); or some such.
--
You received this message because you are subscribed to the Google Groups "fltk.general" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fltkgeneral+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/fltkgeneral/9105070a-0521-4ca3-942d-849db093209b%40seriss.com.
[ Direct Link to Message ] | |
|
| |