Any errors thrown by Ffmpeg need to be caught. It can also happen that the cleanup fails because file handles in the cache are still open. If you have any other ideas of errors that could arise those should also be caught.
Printing Errors
Errors should be presented in the nicest way possible to the user. Print them in red and try to avoid full stack traces, as they are usually really overwhelming to the end user.
When an error occurs the user should be shown a path to the log file (see #5) and a link to create an issue with this repository.
LectureCut needs better error handling.
This includes
Catching Errors
Any errors thrown by
Ffmpegneed to be caught. It can also happen that the cleanup fails because file handles in the cache are still open. If you have any other ideas of errors that could arise those should also be caught.Printing Errors
Errors should be presented in the nicest way possible to the user. Print them in red and try to avoid full stack traces, as they are usually really overwhelming to the end user. When an error occurs the user should be shown a path to the log file (see #5) and a link to create an issue with this repository.