Kovid, still haven't had time to dig out the old computer, but I wanted to comment that the foreground processing isn't an issue for me. If I have to wait, I wait.
You're probably right, it is probably a spinner instead of a progress bar. But if so, it still never reaches 100%. The dialog stops at one step short of 100% (relative to the number of books being processed) and maintains that display while the foreground process wraps up and control is returned to the user. Again, on an older computer, this can be several minutes (yes, I timed it once at 4+ minutes).
I guess, psuedo-code wise, I could describe what I'm seeing as a Do Until loop where the Percent Complete and Update Dialog sub-routines are only called in after the loop is incremented. At which point, since the loop has hit 100, the dialog never gets to the final run of those sub-routines. So although the task is 100% complete, the dialog is sitting at 93.5% complete (per previous example).
Add in the user's slow computer and thus the "Ut oh, I think it's frozen" user perception I mentioned previously as the foreground processing cleans up and returns control to the user.
Last edited by Sabardeyn; 10-22-2013 at 05:54 PM.
Reason: Clarity.
|