Error reporting for plugin rendering API

[hn_netlabs_trac@…]

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)

[Eugene Romanenko]

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

[ktk]

Could you report that as well for 1.2?

[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.

[Lewis Rosenthal]

Milestone renamed

[Lewis Rosenthal]

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.

See:

• renderPageToPixbuf
• renderPageToPixbufAsynch
• renderPageToPS