Thread: Choppy GUI

I have developed a program using the Qt library for my GUI. I had been using borland to compile my program, but due to a need for non-borland compatible libraries in another project I have switched over to MSVC++ .Net. I did not get the full visual studio package so I do NOT have the optimized compiler.

My problem is the GUI tends to be a bit choppy. Moving a dialog box around creates a tail effect. Using the full screen button, the window immediately filles up the full screen, but the Qt widgets will not reposition themsleves without a second delay or so.

I did not have this problem at all with borland, so I am pretty sure the problem lays with MSVC++. I do not know if the optimized vs. non-optimized compiler is creating a problem.

Any help would be greatly appreciated.

Since you were using non standard techniques with the borland compiler, there is some thing that you have forgotten to change when you changed to MSVC. It wouldn't be the compiler directly but the way you are using it. I have never used Qt so that is all I can say.

My problem is the GUI tends to be a bit choppy. Moving a dialog box around creates a tail effect. Using the full screen button, the window immediately filles up the full screen, but the Qt widgets will not reposition themsleves without a second delay or so.

That's odd. I've never used QT but you might be able to get hints at what's wrong by breaking within the second delay and then doing a stack trace.

I did not have this problem at all with borland, so I am pretty sure the problem lays with MSVC++. I do not know if the optimized vs. non-optimized compiler is creating a problem.

Unlikely, I think. You'd probably have more problems with the optimizing compiler. But perhaps the msvc++ compiler is linking with a debug version of QT that does some kind of logging or expensive background checks.

Turns out it is a problem caused by a widget I use that allows me to display visualizations created with the vtk library in my Qt windows. I recently changed to a new version of this and didn't consider that it might be the culprit.

Thanks to those of you that offered your help.