wilderjds/kwin - kwin - gitea-jacopods

10948 Commits

36 Branches

0 Tags

96 MiB

Tag: Branch: Tree: d85802da4e

Commit Graph

Author	SHA1	Message	Date
Martin Gräßlin	330d40f425	Fix no cast to/from ASCII intrduced issues * "" needs to be wrapped in QStringLiteral * QString::fromUtf8 needed for const char* and QByteArray * QByteArray::constData() needed to get to the const char*	13 years ago
Martin Gräßlin	1d2c2d5982	Use Q_SLOTS and Q_SIGNALS instead of slots and signals Fixes compilation with Qt5/KF5 setup.	13 years ago
Martin Gräßlin	1d959dea64	Move Desktop Chain management from Workspace into own class Most recently used virtual desktop chain is only used in the context of TabBox and therefore moved into this namespace. KWin uses one desktop chain for each activity. This is mapped by having multiple DesktopChains. In addition there is a DesktopChainManager which contains all those chains which are identified by a QString. The manager gets connected to the signals emitted by VirtualDesktopManager for changes in virtual desktops and to signals related to Activities emitted by Workspace. This means the manager is rather generic as it does not depend on any other components.	13 years ago

Author

SHA1

Message

Date

Martin Gräßlin

330d40f425

Fix no cast to/from ASCII intrduced issues

* "" needs to be wrapped in QStringLiteral
* QString::fromUtf8 needed for const char* and QByteArray
* QByteArray::constData() needed to get to the const char*

13 years ago

Martin Gräßlin

1d2c2d5982

Use Q_SLOTS and Q_SIGNALS instead of slots and signals

Fixes compilation with Qt5/KF5 setup.

13 years ago

Martin Gräßlin

1d959dea64

Move Desktop Chain management from Workspace into own class

Most recently used virtual desktop chain is only used in the context of
TabBox and therefore moved into this namespace. KWin uses one desktop
chain for each activity. This is mapped by having multiple DesktopChains.
In addition there is a DesktopChainManager which contains all those
chains which are identified by a QString.

The manager gets connected to the signals emitted by VirtualDesktopManager
for changes in virtual desktops and to signals related to Activities
emitted by Workspace. This means the manager is rather generic as it does
not depend on any other components.

13 years ago

3 Commits (d85802da4ef6e2b69aa87dada975cd81fceee7fa)