MobileRead Forums - View Single Post

capink · 11-10-2022, 06:01 AM

That is because I am able to detect the jobs easily by:

Query the job manager of all running job ids immediately before the action is launched and storing them.
Query the job manager of all running job ids immediately after the action is launched and storing them.
Figuring out which jobs were started by the action itself, by subtracting the first set of job ids from the second set.
Keep blocking the GUI until all the jobs started by the action are finished.

I never used any of the plugins you cited, and have no experience with proceed_question. If anyone can provide the code to detect proceed_question dialog in the middle of the action in a robust way, I will add it to the plugin.

11-10-2022, 06:01 AM	#957
capink Wizard Posts: 1,204 Karma: 1995558 Join Date: Aug 2015 Device: Kindle	That is because I am able to detect the jobs easily by: Query the job manager of all running job ids immediately before the action is launched and storing them. Query the job manager of all running job ids immediately after the action is launched and storing them. Figuring out which jobs were started by the action itself, by subtracting the first set of job ids from the second set. Keep blocking the GUI until all the jobs started by the action are finished. I never used any of the plugins you cited, and have no experience with proceed_question. If anyone can provide the code to detect proceed_question dialog in the middle of the action in a robust way, I will add it to the plugin. Last edited by capink; 11-10-2022 at 06:10 AM.