to show that some longer action was running you could use some code like this in the past: mw.progress.start() # some action mw.progress.finish() see e.g. Damien’s Basic Printing Support add-on, source . Up to version .44 this code in an add-on gave you a spinning wheel while the action was runnin…

I added some notes about this to the docs today: https://addon-docs.ankiweb.net/background-ops.html

(the fact that direct calls worked in the past was due to ugly hacks that updated the UI when progress.update() or the DB progress hook was called - these resulted in choppy updates, and could lead to crashes)

dae: Thank you very much. Your step-by-step is very useful for someone like me. Rumo: I could/should have thought of checking this …

@dae Could you add some documentation on how to update the progress bar in this case? Also I think there is some errors in the documentation code. The function is name “my_background_op” in the def but “my_background_operation” elsewhere. Also the loop variable is called id, but then the loop uses …

Thank you, I’ve fixed the incorrect function name. That page has an example of how progress can be updated from within the op - see the “run_on_main” part.

Hi there, I’ve been checking the docs and the source and just want to understand in this thread – if I’m using QueryOp, the UI shouldn’t lock up with a spinner and the user should be able to do whatever at that time, right? And if I call .with_progress() the user should be able to see a progress ba…

With the snippet below (in Anki’s REPL) you can see that the behaviour is exactly like you described. I would incrementally add your logic to it until it stops working. from aqt.operations import QueryOp def sleep(_): import time time.sleep(3) for i in range(10): op = Que…

There is some overhead when running a background op, so you typically want to make an operation that does all the work in one go, instead of creating lots of separate operations for each id. If you want bounded parallelism (eg 4 network requests in flight), then you’ll need to roll your own solution…

Yeah, perhaps it’s an issue of volume, in this case I was kicking off about 1 op per card and testing it on anywhere from 30-50 cards. With the on_success callback it shouldn’t be too hard to implement a loop or some type of queue to throttle the rate of the ops.

Thanks a lot for the fast response.

Progress indicator (mw.progress.start) in .45+ / basic printing support

Anki Development

Rumo November 25, 2021, 8:13am 2

I think you’re supposed to use QueryOp or CollectionOp now.
Also see Add-on porting notes for Anki 2.1.45.

Topic		Replies	Views
Custom progress updates not showing up in CollectionOp run in sync_did_finish Development	7	182	February 7, 2025
Asynchronous calls from an addon Development	3	127	February 11, 2025
Race condition when running background task Development	8	556	May 13, 2022
Mw.progress.start() is not showing progress Add-ons	1	451	April 26, 2022
Pause/Disable Backups during background tasks Development	6	100	March 15, 2026

Progress indicator (mw.progress.start) in .45+ / basic printing support

Related topics