Asynchronus behaviour causing problems with the OCX, C# .NET
At this time we have a chart in our qvw that still is performing quite slow, not due to QV, its really our data-structure.
But meanwhile another developper want to start working with some automation. W've noticed that quite some commands are send to the OCX, then the OCX start updated some chart that are on the tabsheet.
But the .NET software is alreay in control again, of has focus ... meaning that it could continue its work and the ocx is still updating.
Is there a way we can 'sense' that the ocx is still processing/busy so that we can wait for it .....
