I don't understand the problem. If its a long running task, then it should sleep or at least yield from time to time (some Lr methods do this so you don't have to, but something has to...), in which case the progress bar is doing what it should, no?
I mean, if you are going to access the catalog for a long time, there's the catalog:with-prolonged-write-access-do method, otherwise just leave the progress bar up until you're done and sleep/yield from time-to-time, no??
And of course there's also the progress-scope in the upper left corner if modal is not required.
What am I missing?
I think sschultz lr3 is saying that the model progress dialog doesn't appear unless there's the call to sleep(). It seems similar to the problem described in this thread:
I have encountered a slightly different intermittent problem, where the progress dialog doesn't go away:
Inserting a call to sleep() works here too.
I realize its anomalous, but once you know what to do for it to work, is there still a problem?
PS - I wonder why this sort of thing does not get fixed in dot releases.
E. Scouten was aware of the problem. Where in the world is Chet Drarvik???!!!