Hello,
On Sat, 23 Dec 2006 18:49:10 +0100, Christopher Martin
<[EMAIL PROTECTED]> wrote:
On Tuesday 19 December 2006 17:39, Jiří Paleček wrote:
Open a big image (eg. a photo from 3MPix camera), set zoom to "fit to
window".
Then, work with the menus. If you have some top-like program running,
it would show you gwenview is using 100% CPU for (not so short)
periods of time.
It sounds like Gwenview is taking a lot of CPU to process the image the
image to fit the window. Some CPU usage here is unavoidable, and while
that processing is occurring, the rest of the GUI is going to be
(unavoidably) slowed and less responsive. What setting do you have
for "Settings --> Configure Gwenview --> Image View, Smoothing? Try
changing it to Fast or None. The Best setting, for instance, is very
high quality, but does indeed take an _enormous_ amount of CPU time and
power.
So let me know if lowering that setting improves the situation.
Well, yes and no. I lowered the settings to Fast, and it's slightly
faster. However, I don't think that the smoothing time should be a
problem. The problem is that Gwenview smoothes the image every time
it needs repaint, and that it seems to do that to the whole image.
The situation is not that the GUI is unusable for short periods
of time after loading an image, as you have proposed. It is unusable,
for example, when you open a menu which will obstruct the image
and then open another menu -- you will have to wait for the former
menu to close, and the image to repaint.
For example, when in fullscreen mode, the OSD (the sliding blue thing
in the top-left corner of the screen) is almost unusable because you
have to wait for numerous repaints (and smoothings).
Also, the earlier version was much better in this.
Reagrds
Jiri Palecek
