In the old version of the code, these operations were virtually
instantaneous; with the new version, you can actually watch the
individual controls change, and it can take several seconds (!)
to reload them all. I've tried adding .Freeze() and .Thaw()
calls in the hope that this would make it faster, but this only
makes the change appear to hesitate for the same interval, and
then update all at once. The lag is so noticeable that I feel
like there ought to be wait cursor, but I can't help but feel that
loading up 20-40 controls with values *should NOT* take this
long! (and didn't before...)
I don't remember noticing a slowdown of that magnitude, or really any
slowdown at all. Are you sure it is wxPython? Perhaps it could be
some portion of your application that is doing some operation that is
taking a long time to execute.
Yep, I'm sure... I just made the minimal changes required to
make my 2.6 application work again with 2.4, this time retaining
the wx. syntax everywhere but where absolutely necessary,
and then swapped out the wx 2.6 library with 2.4. With 2.4,
the updates are acceptably fast, but with 2.6, they aren't,
by a long shot...
In the old version of the code, these operations were virtually
instantaneous; with the new version, you can actually watch the
individual controls change, and it can take several seconds (!)
to reload them all. I've tried adding .Freeze() and .Thaw()
calls in the hope that this would make it faster, but this only
makes the change appear to hesitate for the same interval, and
then update all at once. The lag is so noticeable that I feel
like there ought to be wait cursor, but I can't help but feel that
loading up 20-40 controls with values *should NOT* take this
long! (and didn't before...)
I don't remember noticing a slowdown of that magnitude, or really any
slowdown at all. Are you sure it is wxPython? Perhaps it could be
some portion of your application that is doing some operation that is
taking a long time to execute.
Yep, I'm sure... I just made the minimal changes required to
make my 2.6 application work again with 2.4, this time retaining
the wx. syntax everywhere but where absolutely necessary,
and then swapped out the wx 2.6 library with 2.4. With 2.4,
the updates are acceptably fast, but with 2.6, they aren't,
by a long shot...
Are you seeing this on multiple platforms, or one in particular? Also, what kinds of controls are you updating, and are you doing anything in threads? On platforms I support, I see no performance degradation in 2.6 so I somewhat doubt this is an issue with 2.6 just being slower in general. What's I think more likely is that there's a wx bug that your code is causing to surface.
As for ways to help track this down, I'd first recommend trying 2.8 and seeing if it still has the same issue. If so, I'd suggest either posting some code showing the problem here (if you can), or adding print statements to various points in the control updating code to see precisely where the code starts to become slow, and then speeds up again.
Regards,
Kevin
···
On Dec 12, 2006, at 6:27 PM, Will Sadkin wrote:
Will Sadkin <WSadkin@Parlancecorp.com> wrote:
?
/Will
---------------------------------------------------------------------
To unsubscribe, e-mail: wxPython-users-unsubscribe@lists.wxwidgets.org
For additional commands, e-mail: wxPython-users-help@lists.wxwidgets.org