GitLab

Connect anti-aliasing combobox to currentIndexChanged signal.

REVIEW: 117957
BUG: 324728
FIXED-IN: 4.11.11

and copy isSpecialWindow() check as rulebook input
to setFullscreen()

Client::isFullScreenable() checks:
* fullscreen rule
* fullscreen_hack (-> for normal windows)
* geometry restrictions
* special window

Client::manage() for fullscreeining checks:
* fullscreen rule (with correct "initial" parameter)
* fullscreen_hack

-> this breaks the fullscreen rule for geometry restricted windows
and causes inconsistent behavior between client requests at runtime
(which do not test ::isFullScreenable()) and on mapping.

Otoh, the specialWindow() protection should apply generally - those
kind of windows should not be fullscreened since the user can not
exit this state via kwin for them - and there's hardly a good reason
for them to be fullscreen, esp. not to enter that state at runtime

REVIEW: 118442
BUG: 335617
FIXED-IN: 4.11.12

REVIEW: 118537
BUG: 333012
FIXED-IN: 4.11.12

After resuming from suspend, all batteries are added
to powerdevil. When a battery, with charge lower or
equal than the critical charge percentage is added, the
critical battery timer will be started.

In the current version the critical battery timeout can
only be interrupted by plugging in AC.

But if the system has more than one battery, the global
charge percentage can be greater than the critical charge
percentage and so the system shouldn't suspend. To achive
this behaviour, we calculate the global charge percentage
whenever a new battery was added and if the critical
battery timer is running and the global charge is high
enough, we stop the timer.

Also we use the already calculated global charge percentage
for the battery charge percentage notification instead of
the charge of each individual battery.

With this patch, the user can not only interrupt the critical
timer by plugging in the AC but also by plugging in a new or
additional battery (if the battery has enough charge).

Note: The 30 sec timeout message will still popup.

Tested with a Thinkpad T440s (two batteries)

@Philipp Paris: Thanks for testing!

BUG: 329537
BUG: 325707
FIXED-IN: 4.11.11
REVIEW: 118801

CCBUG:325944

CCBUG: 336128

As discussed in https://git.reviewboard.kde.org/r/117091/. Not using the
SA_RESTART flag might (in theory) cause the greeter to be aborted
(because certain syscalls may be interrupted and fail with EINTR).
SA_RESTART seems to be the BSD default and is used by "legacy" signal()
by default in glibc 2 and later as well anyway.

REVIEW: 118563

clearly, i never tested that code. :}

found by Stefan Brüns <stefan.bruens@rwth-aachen.de>

huge windows are not contrained to their initial screen
(the user might want to move them to the other instead),
but we must not let them drop out of the fullscreen area
either

CCBUG: 335043
REVIEW: 118412

BUG: 334152
REVIEW: 118411
FIXED-IN: 4.11.10

BUG: 334391
FIXED-IN: 4.11.10
REVIEW: 118050

The Scene connects to the deletedRemoved signal and tries to remove the
Deleted from it's list of Windows, which will fail because a SceneWindow
doesn't get created for an existing Deleted in the Scene setup.

It doesn't make sense to create a SceneWindow for a Deleted as there is
no pixmap around anyway. Thus the best approach is to ensure that there
are no Deleted by just discarding all prior to creating the Scene.

BUG: 333275
CCBUG: 334273
REVIEW: 117557

"cherry-picked" from kwin.git 8e631028552c4b474a317ebf589e31c13289c6fd
Author: mgraesslin
Date: Mon, 14 Apr 2014 09:19:43 +0200

geometryChanged is always executed before maximizeChanged, so we
store the last changed geometry (through regular resize - the current
geometry) and the second last one (used exclusively so far) which is
the old geometry we want to use if the geometry change was caused
by the maximize change

BUG: 335023
FIXED-IN: 4.11.10
REVIEW: 118409

CCBUG: 315346

This fixes the issue with cut off titles for font size around 15 pt and bigger. The correct display of large fonts is neccesary for users with impaired vision.
REVIEW: 118141