BUG:274523

don't update the size with a queuedconnection, instead, delay emission
of preferredsizechanged from addWidgetsForTask
BUG:274525

CCBUG: 274177

CCBUG: 274177

Replaced 1280x1024 background with the correct one because (background was 1278x1024 instead of 1280x1024).
BUG: 273731

BUG:257783

with a queue connection, it updates the preferred size at the loop after
removing an entry from the tray.
in this way, the proper updated size gets used
BUG:274352

BUG:274472
BUG:274475

BUG:274493

BUG:274490

BUG:274468

qDeleteAll knows how to delete values of the map/hash in a better way than calling values

For what reason ever motion manager thinks that windows are not
moving during the start animation (but are during the stop animation).
So we also have to look on the timeline to decide whether we should
disable lanczos filter on the windows.

Now wonder the animation was stuttering.
BUG: 274292
FIXED-IN: 4.7.0

probably not the fix for the bug below, but certainly an improvement over the
reported behavior

BUG:209004

The logic to prevent errornous desktops broke setting a window
to all desktops through the task manager. For some reason all
desktops is -1 which is of course less than 1 ;-)

- Method is now called (once) in Style::polish() so that it is late enough for the style to detect QApplication
vs KApplication (namely, not in QApplication constructor).
- Activate KGlobalSettings only for QApp (not KApp) cases, because it is already done in KApplication
constructor, and might actually conflict.

REVIEW: 101430

CCMAIL:montel@kde.org

Somehow gcc does not care about the ctor because it's a template and this
ctor isn't used anywhere.

CCMAIL: kde@michael-jansen.biz

this avoids that clock jumps (e.g., ntp syncs) cause timeouts.
fixes bug 269522