OK, problem has been removed, though I do not know what the problem was.
The issue was that MatPlotLib did not go together with the rest and
simply got the whole program to a stand-still. I have not had the time
to check what really was the problem, but it seemed obvious that a long
queue of ev
PS: playing more it is not only the spin box. Other actions taken on the
interface slow it down too. Thus it is not a problem with the spin
boxes, but must be more generic. Only noticed the problem there first.
On 09/22/2010 04:48 PM, Preisig, Heinz A wrote:
Certainly:
I am using a timer to g
Certainly:
I am using a timer to generate time events. On each time event I am
doing a computation, in this case a data acquisition (DA converter) and
then a computation the result of which is sent to a DA converter. The
interface has a couple of spin boxes and sliders and buttons to
manipula
On Wednesday 22 September 2010, 15:45:15 Preisig, Heinz A wrote:
> I observed that when using integer spin boxes in a timed loop the
> performance drops significantly after changing a value.
Heinz, could you elaborate on "using integer spin boxes in a timed loop" a
bit, please? I don't grasp the
I observed that when using integer spin boxes in a timed loop the
performance drops significantly after changing a value. After dxchanging
them by double spin boxes no deterioration was observed.
Heinz Preisig
___
PyQt mailing listPyQt@riverbankco
