I am working on an application where I am responding to a midi controller then trying to reflect the value on a filmstrip slider. The application is mixer with several windows open showing different views that I place on different monitors. The maincomponent window contains channel faders (variable number) and a second window called masterdlg(simple dialog window)contains faders for master/aux and busses.
When a midi controller is received, the controller is mapped to a window and fader control and uses setValue to move the fader. On the maincomponent window, the faders move very quickly with almost no delay. But on the masterdlg window they move very slowly.
If I move one fader quickly from 0 to 100% then back to 0, the fader takes about 10 second to reach 100% and another 10 to go back to 0. (running compiled in debug but in release mode its a bit faster but still painfully slow).
If I move another fader while the first is moving, it will not move until all the moves on the first are complete. I have tried using callFunctionOnMessageThread and there is no noticable difference.
The code between the maincomponent window and the masterdlg are almost identical.
Does anyone have any idea why this would be? Something different in the way the maincomponent works over a dialog window?