View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0013050 | Scribus | Usability | public | 2015-05-06 20:35 | 2015-06-15 13:33 |
| Reporter | Kunda | Assigned To | |||
| Priority | normal | Severity | feature | Reproducibility | have not tried |
| Status | new | Resolution | open | ||
| Platform | Mac | OS | OSX | OS Version | 10.9.5 |
| Product Version | 1.5.0svn | ||||
| Summary | 0013050: [Feature] Add optional info box in GUI for debug purposes and reporting more indepth errors | ||||
| Description | There are many bugs/features requesting more 'behind the scenes' info about: * what caused a specific crash, 0008430 * why a file format didn't import correctly 0005941, #4945, 0009078, 0009159, 0012074, 0012187 * helping understand why a function didn't execute correctly (perhaps a plugin or script etc...) * seeing debug output of certain functions etc. | ||||
| Additional Information | As Vlada mentions in 0005941:0026807 "Don't we already support this by writing unsupported features to terminal? How hard would it be to pop up info box in GUI too?" | ||||
| Tags | No tags attached. | ||||
| Patch | No | ||||
| parent of | 0005941 | acknowledged | Add optional (geeky) extender for listing of unsupported SVG features that had been discarded on import | |
| parent of | 0009078 | confirmed | Incorrect Import of SVG File. | |
| parent of | 0009159 | new | PDF form fields don't import correctly | |
| parent of | 0012074 | assigned | fschmid | Missing warning if an ODG file contains unsupported features |
| parent of | 0012187 | new | SVG not well imported | |
| parent of | 0008612 | new | better warning when opening of a .sla failed | |
| parent of | 0008430 | new | Provide detailed feedback as to what's wrong when crashing when opening document | |
| related to | 0012183 | new | No message for warnings when importing PDF | |
| Not all the children of this issue are yet resolved or closed. | ||||
|
|
this feature must be well planned in order not to slow scribus down and not make the code even more unreadable than it currently is. one idea is to use the standard error for this. when scribus catches something strange it could output a message to the standard error (the terminal by default). a preference could be added to get scribus to redirect the output of qDebug() to a specific file... that should be possible... storing the the undo list in the doc and being able to export it, might also be of help... so we know "exactly" what the user did... just some ideas... |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2015-05-06 20:35 | Kunda | New Issue | |
| 2015-05-06 20:36 | Kunda | Relationship added | related to 0005941 |
| 2015-05-06 20:36 | Kunda | Relationship replaced | parent of 0005941 |
| 2015-05-06 20:36 | Kunda | Relationship added | parent of 0009078 |
| 2015-05-06 20:37 | Kunda | Relationship added | parent of 0009159 |
| 2015-05-06 20:37 | Kunda | Relationship added | parent of 0012074 |
| 2015-05-06 20:37 | Kunda | Relationship added | parent of 0012187 |
| 2015-05-06 20:39 | Kunda | Additional Information Updated | |
| 2015-05-06 20:45 | Kunda | Relationship added | parent of 0008612 |
| 2015-05-07 06:57 | ale | Note Added: 0035060 | |
| 2015-05-08 00:40 | Kunda | Description Updated | |
| 2015-05-08 00:40 | Kunda | Relationship added | parent of 0008430 |
| 2015-05-19 18:38 | Kunda | Relationship added | related to 0012183 |
