Bug 198469

Summary: SVGs should be re-rendered asynchronous for resize operations
Product: [Unmaintained] kdelibs Reporter: Clemens Eisserer <linuxhippy>
Component: generalAssignee: kdelibs bugs <kdelibs-bugs-null>
Status: RESOLVED UNMAINTAINED    
Severity: wishlist CC: plasma-bugs-null
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Clemens Eisserer 2009-07-01 00:00:15 UTC 
Version:            (using KDE 4.2.90)
OS:                Linux
Installed from:    Fedora RPMs

Many places where svg icons need to be re-rendered behave quite unresponsive, because the svg-rendering blocks the operation.
This is true especially for resize operations.
A good example is resizing plasma panel's, or resizing Dolphin's "Places"-panel.
Especially for larger sizes resizing gets more and more unresponsive and stuttering.

A better approach would be to re-render svg's in a seperate background thread and paint them when rendering is done. Often smooth resizing is more important, then an instant look.

This approach would also have the advantage, that not all sizes for a resize operation would have to be generated. 
If e.g. resizing a panel from 20px to 40px in 4px steps would normally generate 5 re-render events, doing it in a seperate thread sizes between could be canceld - because they simply could be canceld out of the queue of waiting svg's if the background thread can't keep up.
Comment 1 Clemens Eisserer 2010-06-11 01:10:15 UTC 
4.4.80 - performance is still bad
Comment 2 Clemens Eisserer 2010-10-29 15:13:31 UTC 
4.5.2 - resing SVG rendered content still horrible slow.
Try to resize plasmoids on a 1920x1200 display, its like a slideshow.
Comment 3 Christoph Cullmann 2024-09-14 16:18:35 UTC 
Hi,

kdelibs (version 4 and earlier) is no longer maintained since a few years.

KDE Frameworks 5 or 6 might already have implemented this wish.

If not, please re-open against the matching framework if feasible or against the application that shows the issue.

We then can still dispatch it to the right Bugzilla product or component.

Greetings
Christoph Cullmann