[mythtv] Ticket #7916: Automatically save cutlist during editing

Michael T. Dean mtdean at thirdcontact.com
Thu Sep 16 22:17:57 UTC 2010


  On 09/16/2010 04:01 PM, Jim Stichnoth wrote:
> On Thu, Sep 16, 2010 at 11:06 AM, Michael T. Dean wrote:
>> I think if auto-save is implemented using a new "temporary" mark type that's
>> not an actual cut list mark type (not MARK_CUT_START/END), but that gets
>> converted to a real cut list when the user (explicitly) saves, it provides
>> the best of both worlds.  It always auto-saves as the user works, but
>> doesn't ever save a partial/incorrect cut list to the database.
> I like this idea very much.  A couple of questions:
>
> 1. If the user exits without saving, should the temporary marks be
> left in the DB for later recovery?

I'd say exit without saving and explicit revert should both remove 
them--for consistency and as a principle of "least surprise".  I can't 
really see any justification for adding another option to allow a user 
to save a work-in-progress cut list.  In theory, if they've corrected 
any of the marks from the flag list or put in some correct marks 
manually, it's better than it was to start with, so they might as well 
just save them officially.

Exiting via jump point could go either way.  Coder's choice?

"Exiting" with a crash would, obviously, leave the temporary marks in 
place in the DB.

That said, I don't have a vested interest in any particular approach 
(since I'll have seen the code and know how it works, I'll be able to 
make it do what /I/ want), so as long as you come up with a good 
rationale for the approach you choose, I could be convinced to go 
another way.

Do any UI folks have any input?

> 2. What happens when the user starts to edit and temporary marks are found?
> a) Load them automatically
> b) Prompt the user (this prompt could be integrated with the
> recorded.editing prompt)

Either approach works for me.  The prompt would remind the user these 
are "in progress" marks, but that could also be done with just a notice 
rather than a prompt.  If the most-common occasion a user would re-load 
these temp marks would be after a crash, though, it may just be rubbing 
salt on the wound if we also make them work harder to get back to 
editing. :)

Again, I'll leave this to the UI folks.

Mike


More information about the mythtv-dev mailing list