Opened 13 years ago

Last modified 13 months ago

#42 new enhancement

Error reporting for plugin rendering API

Reported by: hn_netlabs_trac@… Owned by:
Priority: major Milestone: 1.4.2
Component: Lucide Core Version: 1.0 Beta 1.1
Keywords: Cc:


When rendering a document page certain errors could arise in the plugin (e.g. out-of-memory, file no longer accessible, ...).

It is so far not possible for a plugin to report these errors to the Lucide core. Thus the user has no idea what went wrong. He/she probably just sees an empty page (or crap).

Proposal: Apply the same error reporting scheme used for loadFile() to renderToPixbuf() and renderToPS(). (boolean returned, error message via SOMMalloc)

Change History (7)

comment:1 Changed 13 years ago by eros2

Done in changeset [155], but render errors isn't disaplayed yet.

comment:2 follow-up: Changed 11 years ago by ktk

  • Milestone set to 1.2

Could you report that as well for 1.2?

comment:3 in reply to: ↑ 2 Changed 11 years ago by guest

Replying to ktk:

Could you report that as well for 1.2?

Yes. The error message passing in the plugin API was implemented long ago but as already noted by eros2, the error message is so far simply thrown away and not shown to the user.

A possible presentation could be either a simple message box or, more sophisticated, a status bar.

GBM plugin is using the error reporting from the beginning. Don't know if lupdf, lujpeg or ludjvu are ready as well.

comment:4 Changed 4 years ago by lewisr

  • Owner eros2 deleted

comment:5 Changed 4 years ago by lewisr

  • Milestone changed from 1.4 to 1.4.0

Milestone renamed

comment:6 Changed 3 years ago by lewisr

  • Milestone changed from 1.4.0 to Future

Related to #311

Need to add guidelines for plugin developers to ensure that they are using this once we start presenting error messages to users.


comment:7 Changed 13 months ago by gyoung

  • Milestone changed from Future to 1.4.2
Note: See TracTickets for help on using tickets.