View Single Post
Old 06-25-2013, 05:36 PM   #5
BetterRed
null operator (he/him)
BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.
 
Posts: 21,645
Karma: 29710510
Join Date: Mar 2012
Location: Sydney Australia
Device: none
@dandichka like Sabardeyn I read your post and decided I couldn't give you a straightforward response so I also decided it was best left to the experts - although I do have some empathy the issue you've raised.

I don't know if it would be feasible to implement what you suggested - which as I read it is :-
  • When a job finishes that requires user input then suspend current user input and give control to the end of job user input
  • When the end of job user input is finished resume the user input that was suspended
  • The first question this raises in my mind is what happens if another job finishes whilst another has control of user input, does it take over?.
  • It sounds like a tricky thing to implement and a difficult thing for many users to manage - I know I'm not good at handling interrupt stacks - I only allow one call waiting on my phone, any further calls go to voicemail.
An alternative might be to put the jobs that are awaiting user input into an end of job user input pending queue
  • I'd suggest only those jobs involving multiple books would put themselves into this queue - and only then if an appropriate tweak is set to True (its default would be False to reflect the status quo)
  • The Jobs Spinner be given a different colour or some other hint if there's are entries in the end of job user input pending queue.
  • There would have to be enhancements to the Jobs dialogue box to facilitate dealing with jobs awaiting end of job user input
  • And calibre may need to issue a warning if the user attempts to terminate it and there are jobs in the end of job user input pending queue; I don't imagine its the sort of data that would persist across calibre 'sessions'.
But I'm not sure how many people would make use of such a feature, which is one of the factors that Kovid and other developers take note of in their deliberations on enhancements to calibre.

Since the current cell highlight feature was introduced I find that I'm doing a most single book edits on the spreadsheet; and its in this context I've noticed and resented the interrupts from end of job dialogues.

Now I only use the edit metadata dialogue for bulk updates and for maintaining my Comment like "Notes" custom column (which I would prefer to do from the Book Details panel - buts that's another 'big ask').

BR

Last edited by BetterRed; 06-25-2013 at 05:44 PM. Reason: grammar & ambiguity
BetterRed is offline   Reply With Quote