In the situation where the print operation fails, it'd be nice for a leaflet event to be fired signifying this (e.g. "easyPrint-failed" to go alongside "easyPrint-start" and "easyPrint-finished").
Currently there is no way of telling if a print operation has failed, because all errors are caught and only logged to console.
The use case of this is having an application enter one state when "easyPrint-start" is fired to then return to the original state on "easyPrint-finished" (or "easyPrint-failed"). Without a way to detect errors, the application is stuck in the state where it thinks easyPrint is still printing.
In the situation where the print operation fails, it'd be nice for a leaflet event to be fired signifying this (e.g. "easyPrint-failed" to go alongside "easyPrint-start" and "easyPrint-finished").
Currently there is no way of telling if a print operation has failed, because all errors are caught and only logged to console.
The use case of this is having an application enter one state when "easyPrint-start" is fired to then return to the original state on "easyPrint-finished" (or "easyPrint-failed"). Without a way to detect errors, the application is stuck in the state where it thinks easyPrint is still printing.