You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: