[Assimp-discussions] ProgressHandler extension

[Gargaj / C. <ga...@co...>]

Hey,

I had an idea for the progress handler, and how to make it more
slightly predictable: (I'm working with ~50-60MB meshes, so I could
use a progress bar)
What if there are two functions in the class instead of one? The first
one - let's call it UpdateRead() - is left up to the importer's
discretion to call on occasion. The second one - UpdatePostProcess() -
is called during the postprocess steps (of which there are a fixed
number of, so they're linear). It would be up to the app's discretion
to deal with either of these.

Not exactly a groundbreaking solution, but it would certainly work
better than the current solution. I can provide a diff for a possible
implementation, if needed.

-garg