ConvertToMDEvents displays progress incorrectly

[Alex Buts]

Converting workspace into MD workspace is done in two steps where the first step usually deals with the conversion of whatever is in input workspace into the output data and the second -- converting these data into MDevents and adding this to MDEventWorkspace.

The second step can take considerable time in comparison with the first step, but the algorithm progress is estimated on the basis of doing the first step only.

Progress bar in this case goes from start to 99% and then freezes at the end for considerable amount of time.

Annoying.

[Alex Buts]

refs #5240 MDBoxToChange.h class is more or less functional

also relates to refs #5552

Changeset: 6291ea48ce4532232bcff7484f966b5da74e929d

[Nick Draper]

Moved at the end of release 2.2

[Alex Buts]

refs #5240 MDBoxToChange.h class is more or less functional

also relates to refs #5552

Changeset: 6291ea48ce4532232bcff7484f966b5da74e929d

[Alex Buts]

this ticket depends on #5552 and reasonably (though not ideally) works with current multi-threading implementation.

I think the implementation is satisfactory and all other changes are subject to changes described in #5552.

To testers: run the conversion (preferably on large and unexpected files, I did real MERLIN and MAPS runs) and see if the progress bar you see allows you to reasonably estimate the real progress.

[Dereck Kachere]

Progress bar no longer goes from start to 99% and then freeze; the progress bar updates in stages and gives a reasonable time estimate for completion.

[Stuart Campbell]

This ticket has been transferred to github issue ​6086