El jue, 09-08-2007 a las 23:07 +0900, Jorg Schuler escribi=C3=B3:
> Hi Javier,
> thanks for your patches. I'm currently working through my mail in=20
> reverse order of receipt (not sure if this is the best strategy, but...)
> > I just noticed that after pressing the "save changes" button Gtkpod's
> > and X's CPU usage skyrocketed. It turns out that Gtkpod was making GTK+
> > and X work a sweat by updating the progress bar 50 times a second, even
> > when it changes in average only once in a minute.
> > This patch seems complex [...]
> Could you please check if this less complex patch has the same effect?=20
> If yes, we can submit it.
It seems that the patch is functionally equivalent to mine, but before I
test it, I have a question for you: I see that you retrieve some
information from the widgets. Now, the part I'm not sure, because I'm no
GTK+ wizard, is if in a remote X session this may cause a query to the
remote server, or does GTK+ cache all widget state data locally?
If you don't care, let me know and I'll give it a try as it is. I rarely
use X remotely, so I honestly don't know how Gtkpod generally performs
in that case.
Javier Kohen <jkohen@...>
ICQ: blashyrkh #2361802