AIS_InteractiveContext::UpdateCurrentViewer() build up call queue and slows down to a halt

Hi there,

While working with the CSharp_D3D example, i have noticed that in some operations, like rotate or pan (specially with a complex part in fullscreen), the amount of AIS_InteractiveContext::UpdateCurrentViewer() calls become way too many for the Redraw method to respond to the point that it seems to hang until you stop moving the mouse.

Is there a built in mechanism to provide consistent/adaptative framerate that still leaves room for other operations and events to be attended? Or maybe this issue could be caused by some other reason?

As a side note: In a graphic engine i built some time ago, the requests for redraw were not always attended immediately, but just flagged the redraw, then when the engine saw fit, it will redraw if it was flagged (according to its current frame rate and leaving some few extra ms for other systems to continue working), this way, even if moving the mouse like crazy, the paint was not saturating the system nor the paint requests were queuing up.

Thank you in advance!