New Forum | Previous | Next | (P-PDF) Developers
Topic: Orphaned progress monitors
Conf: (P-PDF) Developers, Msg: 132353
Date: 5/7/2005 02:02 AM
Has anyone encountered this problem?
We use AVAppGetDocumentProgressMonitor, with the usual callbacks beginOperation setDuration setCurrValue endOperation.
In Acrobat 6 on the Mac, the monitor is sometimes orphaned. By that I mean it appears, overlaying the status line of the document, but never goes away. In addition, the bar never moves. It is stuck for good; later progress bars that would appear when that document is active will not cause any change; however other windows can freely show working bars that appear and disappear.
This is predictable and repeatable; some code paths do this, and others don't. The code used is different, but seems to contain all of the same combination of calls, in the same order. The only difference is that AVAppGetDocProgressMeter is called several times in the failing path.
Any clues, before I have to implement a custom progress meter instead?