yukijoou/kwin
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
kwin/autotests/tabbox/test_desktopchain.cpp

253 lines
9.3 KiB
C++
Raw Normal View History

Prettify license headers
2020-08-02 22:22:19 +00:00
/*
KWin - the KDE window manager
This file is part of the KDE project.
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.
2012-11-17 10:50:59 +00:00
Prettify license headers
2020-08-02 22:22:19 +00:00
SPDX-FileCopyrightText: 2013 Martin Gräßlin <mgraesslin@kde.org>
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.
2012-11-17 10:50:59 +00:00
Prettify license headers
2020-08-02 22:22:19 +00:00
SPDX-License-Identifier: GPL-2.0-or-later
*/
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.
2012-11-17 10:50:59 +00:00
// KWin
Make source code more relocatable Occasionally, I see complaints about the file organization of kwin, which is fair enough. This change makes the source code more relocatable by removing relative paths from includes. CMAKE_CURRENT_SOURCE_DIR was added to the interface include directories of kwin library. This means that as long as you link against kwin target, the real location of the source code of the library doesn't matter. With autotests, things are not as convenient as with kwin target. Some tests use cpp files from kwin core. If we move all source code in a src/ directory, they will need to be adjusted, but mostly only in build scripts.
2021-02-09 18:18:36 +00:00
#include "tabbox/desktopchain.h"
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.
2012-11-17 10:50:59 +00:00
#include <QTest>
using namespace KWin::TabBox;
class TestDesktopChain : public QObject
{
Q_OBJECT
Use Q_SLOTS and Q_SIGNALS instead of slots and signals Fixes compilation with Qt5/KF5 setup.
2013-07-22 14:07:39 +00:00
private Q_SLOTS:
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.
2012-11-17 10:50:59 +00:00
void chainInit_data();
void chainInit();
void chainAdd_data();
void chainAdd();
void resize_data();
void resize();
void resizeAdd();
void useChain();
};
void TestDesktopChain::chainInit_data()
{
QTest::addColumn<uint>("size");
QTest::addColumn<uint>("next");
QTest::addColumn<uint>("result");
QTest::newRow("0/1") << (uint)0 << (uint)1 << (uint)1;
QTest::newRow("0/5") << (uint)0 << (uint)5 << (uint)1;
QTest::newRow("1/1") << (uint)1 << (uint)1 << (uint)1;
QTest::newRow("1/2") << (uint)1 << (uint)2 << (uint)1;
QTest::newRow("4/1") << (uint)4 << (uint)1 << (uint)2;
QTest::newRow("4/2") << (uint)4 << (uint)2 << (uint)3;
QTest::newRow("4/3") << (uint)4 << (uint)3 << (uint)4;
QTest::newRow("4/4") << (uint)4 << (uint)4 << (uint)1;
QTest::newRow("4/5") << (uint)4 << (uint)5 << (uint)1;
QTest::newRow("4/7") << (uint)4 << (uint)7 << (uint)1;
}
void TestDesktopChain::chainInit()
{
QFETCH(uint, size);
QFETCH(uint, next);
DesktopChain chain(size);
QTEST(chain.next(next), "result");
DesktopChainManager manager(this);
manager.resize(0, size);
QTEST(manager.next(next), "result");
}
void TestDesktopChain::chainAdd_data()
{
QTest::addColumn<uint>("size");
QTest::addColumn<uint>("add");
QTest::addColumn<uint>("next");
QTest::addColumn<uint>("result");
// invalid size, should not crash
QTest::newRow("0/1/1/1") << (uint)0 << (uint)1 << (uint)1 << (uint)1;
// moving first element to the front, shouldn't change the chain
QTest::newRow("4/1/1/2") << (uint)4 << (uint)1 << (uint)1 << (uint)2;
QTest::newRow("4/1/2/3") << (uint)4 << (uint)1 << (uint)2 << (uint)3;
QTest::newRow("4/1/3/4") << (uint)4 << (uint)1 << (uint)3 << (uint)4;
QTest::newRow("4/1/4/1") << (uint)4 << (uint)1 << (uint)4 << (uint)1;
// moving an element from middle to front, should reorder
QTest::newRow("4/3/1/1") << (uint)4 << (uint)3 << (uint)1 << (uint)2;
QTest::newRow("4/3/2/4") << (uint)4 << (uint)3 << (uint)2 << (uint)4;
QTest::newRow("4/3/3/1") << (uint)4 << (uint)3 << (uint)3 << (uint)1;
QTest::newRow("4/3/4/3") << (uint)4 << (uint)3 << (uint)4 << (uint)3;
// adding an element which does not exist - should leave the chain untouched
QTest::newRow("4/5/1/2") << (uint)4 << (uint)5 << (uint)1 << (uint)2;
QTest::newRow("4/5/2/3") << (uint)4 << (uint)5 << (uint)2 << (uint)3;
QTest::newRow("4/5/3/4") << (uint)4 << (uint)5 << (uint)3 << (uint)4;
QTest::newRow("4/5/4/1") << (uint)4 << (uint)5 << (uint)4 << (uint)1;
}
void TestDesktopChain::chainAdd()
{
QFETCH(uint, size);
QFETCH(uint, add);
QFETCH(uint, next);
DesktopChain chain(size);
chain.add(add);
QTEST(chain.next(next), "result");
DesktopChainManager manager(this);
manager.resize(0, size);
tabbox: Remove unused arg in DesktopChainManager::addDesktop()
2023-02-24 15:06:35 +00:00
manager.addDesktop(add);
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.
2012-11-17 10:50:59 +00:00
QTEST(manager.next(next), "result");
}
void TestDesktopChain::resize_data()
{
QTest::addColumn<uint>("size");
QTest::addColumn<uint>("add");
QTest::addColumn<uint>("newSize");
QTest::addColumn<uint>("next");
QTest::addColumn<uint>("result");
// basic test - increment by one
QTest::newRow("1->2/1") << (uint)1 << (uint)1 << (uint)2 << (uint)1 << (uint)2;
QTest::newRow("1->2/2") << (uint)1 << (uint)1 << (uint)2 << (uint)2 << (uint)1;
// more complex test - increment by three, keep chain untouched
QTest::newRow("3->6/1") << (uint)3 << (uint)1 << (uint)6 << (uint)1 << (uint)2;
QTest::newRow("3->6/2") << (uint)3 << (uint)1 << (uint)6 << (uint)2 << (uint)3;
QTest::newRow("3->6/3") << (uint)3 << (uint)1 << (uint)6 << (uint)3 << (uint)4;
QTest::newRow("3->6/4") << (uint)3 << (uint)1 << (uint)6 << (uint)4 << (uint)5;
QTest::newRow("3->6/5") << (uint)3 << (uint)1 << (uint)6 << (uint)5 << (uint)6;
QTest::newRow("3->6/6") << (uint)3 << (uint)1 << (uint)6 << (uint)6 << (uint)1;
// increment by three, but change it before
QTest::newRow("3->6/3/1") << (uint)3 << (uint)3 << (uint)6 << (uint)1 << (uint)2;
QTest::newRow("3->6/3/2") << (uint)3 << (uint)3 << (uint)6 << (uint)2 << (uint)4;
QTest::newRow("3->6/3/3") << (uint)3 << (uint)3 << (uint)6 << (uint)3 << (uint)1;
QTest::newRow("3->6/3/4") << (uint)3 << (uint)3 << (uint)6 << (uint)4 << (uint)5;
QTest::newRow("3->6/3/5") << (uint)3 << (uint)3 << (uint)6 << (uint)5 << (uint)6;
QTest::newRow("3->6/3/6") << (uint)3 << (uint)3 << (uint)6 << (uint)6 << (uint)3;
// basic test - decrement by one
QTest::newRow("2->1/1") << (uint)2 << (uint)1 << (uint)1 << (uint)1 << (uint)1;
QTest::newRow("2->1/2") << (uint)2 << (uint)2 << (uint)1 << (uint)1 << (uint)1;
// more complex test - decrement by three, keep chain untouched
QTest::newRow("6->3/1") << (uint)6 << (uint)1 << (uint)3 << (uint)1 << (uint)2;
QTest::newRow("6->3/2") << (uint)6 << (uint)1 << (uint)3 << (uint)2 << (uint)3;
QTest::newRow("6->3/3") << (uint)6 << (uint)1 << (uint)3 << (uint)3 << (uint)1;
// more complex test - decrement by three, move element to front
QTest::newRow("6->3/6/1") << (uint)6 << (uint)6 << (uint)3 << (uint)1 << (uint)2;
QTest::newRow("6->3/6/2") << (uint)6 << (uint)6 << (uint)3 << (uint)2 << (uint)3;
QTest::newRow("6->3/6/3") << (uint)6 << (uint)6 << (uint)3 << (uint)3 << (uint)1;
}
void TestDesktopChain::resize()
{
QFETCH(uint, size);
DesktopChain chain(size);
QFETCH(uint, add);
chain.add(add);
QFETCH(uint, newSize);
chain.resize(size, newSize);
QFETCH(uint, next);
QTEST(chain.next(next), "result");
DesktopChainManager manager(this);
manager.resize(0, size);
tabbox: Remove unused arg in DesktopChainManager::addDesktop()
2023-02-24 15:06:35 +00:00
manager.addDesktop(add);
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.
2012-11-17 10:50:59 +00:00
manager.resize(size, newSize);
QTEST(manager.next(next), "result");
}
void TestDesktopChain::resizeAdd()
{
// test that verifies that add works after shrinking the chain
DesktopChain chain(6);
DesktopChainManager manager(this);
manager.resize(0, 6);
chain.add(4);
tabbox: Remove unused arg in DesktopChainManager::addDesktop()
2023-02-24 15:06:35 +00:00
manager.addDesktop(4);
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.
2012-11-17 10:50:59 +00:00
chain.add(5);
tabbox: Remove unused arg in DesktopChainManager::addDesktop()
2023-02-24 15:06:35 +00:00
manager.addDesktop(5);
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.
2012-11-17 10:50:59 +00:00
chain.add(6);
tabbox: Remove unused arg in DesktopChainManager::addDesktop()
2023-02-24 15:06:35 +00:00
manager.addDesktop(6);
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.
2012-11-17 10:50:59 +00:00
QCOMPARE(chain.next(6), (uint)5);
QCOMPARE(manager.next(6), (uint)5);
QCOMPARE(chain.next(5), (uint)4);
QCOMPARE(manager.next(5), (uint)4);
QCOMPARE(chain.next(4), (uint)1);
QCOMPARE(manager.next(4), (uint)1);
chain.resize(6, 3);
manager.resize(6, 3);
QCOMPARE(chain.next(3), (uint)3);
QCOMPARE(manager.next(3), (uint)3);
QCOMPARE(chain.next(1), (uint)3);
QCOMPARE(manager.next(1), (uint)3);
QCOMPARE(chain.next(2), (uint)3);
QCOMPARE(manager.next(2), (uint)3);
// add
chain.add(1);
tabbox: Remove unused arg in DesktopChainManager::addDesktop()
2023-02-24 15:06:35 +00:00
manager.addDesktop(1);
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.
2012-11-17 10:50:59 +00:00
QCOMPARE(chain.next(3), (uint)3);
QCOMPARE(manager.next(3), (uint)3);
QCOMPARE(chain.next(1), (uint)3);
QCOMPARE(manager.next(1), (uint)3);
chain.add(2);
tabbox: Remove unused arg in DesktopChainManager::addDesktop()
2023-02-24 15:06:35 +00:00
manager.addDesktop(2);
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.
2012-11-17 10:50:59 +00:00
QCOMPARE(chain.next(1), (uint)3);
QCOMPARE(manager.next(1), (uint)3);
QCOMPARE(chain.next(2), (uint)1);
QCOMPARE(manager.next(2), (uint)1);
QCOMPARE(chain.next(3), (uint)2);
QCOMPARE(manager.next(3), (uint)2);
}
void TestDesktopChain::useChain()
{
DesktopChainManager manager(this);
manager.resize(0, 4);
tabbox: Remove unused arg in DesktopChainManager::addDesktop()
2023-02-24 15:06:35 +00:00
manager.addDesktop(3);
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.
2012-11-17 10:50:59 +00:00
// creating the first chain, should keep it unchanged
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*
2013-07-23 05:02:52 +00:00
manager.useChain(QStringLiteral("test"));
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.
2012-11-17 10:50:59 +00:00
QCOMPARE(manager.next(3), (uint)1);
QCOMPARE(manager.next(1), (uint)2);
QCOMPARE(manager.next(2), (uint)4);
QCOMPARE(manager.next(4), (uint)3);
// but creating a second chain, should create an empty one
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*
2013-07-23 05:02:52 +00:00
manager.useChain(QStringLiteral("second chain"));
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.
2012-11-17 10:50:59 +00:00
QCOMPARE(manager.next(1), (uint)2);
QCOMPARE(manager.next(2), (uint)3);
QCOMPARE(manager.next(3), (uint)4);
QCOMPARE(manager.next(4), (uint)1);
// adding a desktop should only affect the currently used one
tabbox: Remove unused arg in DesktopChainManager::addDesktop()
2023-02-24 15:06:35 +00:00
manager.addDesktop(2);
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.
2012-11-17 10:50:59 +00:00
QCOMPARE(manager.next(1), (uint)3);
QCOMPARE(manager.next(2), (uint)1);
QCOMPARE(manager.next(3), (uint)4);
QCOMPARE(manager.next(4), (uint)2);
// verify by switching back
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*
2013-07-23 05:02:52 +00:00
manager.useChain(QStringLiteral("test"));
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.
2012-11-17 10:50:59 +00:00
QCOMPARE(manager.next(3), (uint)1);
QCOMPARE(manager.next(1), (uint)2);
QCOMPARE(manager.next(2), (uint)4);
QCOMPARE(manager.next(4), (uint)3);
tabbox: Remove unused arg in DesktopChainManager::addDesktop()
2023-02-24 15:06:35 +00:00
manager.addDesktop(1);
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.
2012-11-17 10:50:59 +00:00
// use second chain again and put 4th desktop to front
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*
2013-07-23 05:02:52 +00:00
manager.useChain(QStringLiteral("second chain"));
tabbox: Remove unused arg in DesktopChainManager::addDesktop()
2023-02-24 15:06:35 +00:00
manager.addDesktop(4);
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.
2012-11-17 10:50:59 +00:00
// just for the fun a third chain, and let's shrink it
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*
2013-07-23 05:02:52 +00:00
manager.useChain(QStringLiteral("third chain"));
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.
2012-11-17 10:50:59 +00:00
manager.resize(4, 3);
QCOMPARE(manager.next(1), (uint)2);
QCOMPARE(manager.next(2), (uint)3);
// it must have affected all chains
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*
2013-07-23 05:02:52 +00:00
manager.useChain(QStringLiteral("test"));
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.
2012-11-17 10:50:59 +00:00
QCOMPARE(manager.next(1), (uint)3);
QCOMPARE(manager.next(3), (uint)2);
QCOMPARE(manager.next(2), (uint)1);
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*
2013-07-23 05:02:52 +00:00
manager.useChain(QStringLiteral("second chain"));
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.
2012-11-17 10:50:59 +00:00
QCOMPARE(manager.next(3), (uint)2);
QCOMPARE(manager.next(1), (uint)3);
QCOMPARE(manager.next(2), (uint)1);
}
QTEST_MAIN(TestDesktopChain)
#include "test_desktopchain.moc"
Reference in a new issue Copy permalink