From: Micha B. <kri...@us...> - 2010-05-02 15:47:28
|
@Vicente I cannot reproduce the behavior here. I have the very same system, except ATI replacing the NVIDIA card. But this shouldn't cause the problem, I think. What kind of threading model is it, that is used in your code? Qt threads? I haven't to much experience with them, but could it be, that your slot misses some kind of Mutex, preventing paint events between updated scaling values but before new data are completely read. Or some similar inconsistency. The things I mean, are mentioned here: http://doc.trolltech.com/4.6/threads-qobject.html#accessing-qobject-subclasses-from-other-threads etc. How about serializing the code, what happens then? A small issue: Could it be, you mix X and Y in the following code sequence: > coords->axes[X1].setTicLength(3*yScale, yScale); > coords->axes[X2].setTicLength(3*yScale, yScale); > coords->axes[X3].setTicLength(3*yScale, yScale); > coords->axes[X4].setTicLength(3*yScale, yScale); > > coords->axes[Y1].setTicLength(3*xScale, xScale); > coords->axes[Y2].setTicLength(3*xScale, xScale); > coords->axes[Y3].setTicLength(3*xScale, xScale); > coords->axes[Y4].setTicLength(3*xScale, xScale); Micha |