ValueError not caught when recent file doesn't exist
Bug #605286 reported by
Jon Black
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Prioritise |
Fix Released
|
Medium
|
Unassigned | ||
Bug Description
When a file in the recent file list is selected, but that file no longer exists, a ValueError is raised which is not caught. The user can continue using prioritise, but this error should be caught and presented to the user in an error dialog box. Additionally, the recent item menu should be removed.
| Changed in prioritise: | |
| importance: | Undecided → Medium |
| Changed in prioritise: | |
| milestone: | none → 0.1.0 |
| Changed in prioritise: | |
| status: | New → Fix Committed |
| Changed in prioritise: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
