> Deletepending means the backend received a message to delete a program,
> so it flagged the program as deletepending so that it would not show up
> in the list of recordings when viewed on the frontend. If you had a crash
> before the backend could delete the file though, the file will still
> exist and the flag will still be set. There is currently no cleanup that
> goes back and looks for old programs marked as deletepending. You can
> do a manual sql update and set those flags back to 0 and then retry
> deleting them in mythfrontend.
>
Interesting. Is there any thought of extending the idea of
deletepending
to the job queue? That is, be able to put a show into a job queue (for example
exporting with nuvexport) and then watch and delete the show while the export
is still running? Once the export was finished, then the delete could proceed
but in the meantime it would be gone from the frontend view.
That's a functionality that I've been thinking about lately as there is
one show that I like to export and watch later, but my wife likes to watch
right away.
The problem is, she can't delete it when she is done watching it because she
doesn't know if I have exported it yet, and even if I have started the export
she doesn't know if it is done. On the other hand, once the export is done, I
can't delete it without making sure she watched it. It's not a *huge* problem
obviously. A close first pass would be a custom "export and delete" job option
that
she could invoke after watching it, though it would still be cooler if it
disappeared from the frontend right away. I'm looking forward to the job queue,
it looks pretty interesting.
-poul
_______________________________________________
mythtv-users mailing list
[email protected]
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
