View Single Post
Old 06-11-2011, 06:40 PM   #55
chaley
Grand Sorcerer
chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.
 
Posts: 11,788
Karma: 7029971
Join Date: Jan 2010
Location: Notts, England
Device: Kobo Libra 2
That change makes sense, assuming I understand what is happening (a dangerous assumption). It calls 'done' on the same thread that runs the job, which is the right thing to do, and perhaps makes the is_gui_thread changes in FunctionDispatcher irrelevant. It clearly does not dequeue the next job until done.

Regardless of whether or not this fixes meme's problem, it is a good change, clarifying the semantics of DeviceJob termination.
chaley is offline   Reply With Quote