You need to derivate at least from QObject. Signal and slots are needed to allow KXDocker works.
Add these methods, as Public SLOTS, to your class returned by the C style entry
xGetParameterList(QStringList *) this will fill the StringList with the Plugin configuration parameters names
xSetupParameter(const QString, const QString) this will set the value of a parameter and write it into XML configuration
xGetParameter(const QString, QString&) return current value of a parameter
xStart() called when before KXDocker show the icon for the first time
xSetup() This the first method called, this will setup the plugin
xStop() KXDocker will call this function before remove the icons, so if you check my code you will see it put the plugin in standby
xParse(const QString &, int, void *) this is an helper slots which can be called by the engine or by other plugins, const QString & describe the action to be done, int represent the index of the icon if known or a void * pointer to a "generic" context, this method is plugin "name" depend.
xGetInfo(QStringList &) fill the String list of plugin descriptions:
You need to implement this methods
Every action done or called by the engine will not always manage al the code, so you need to copy and paste some code to such functions:
Register this plugin into the engine
Stop the plugin and UnRegister this plugin from the engine
// * test is already started
// * allocate sub-classes
// * start internal engine-threads
// * test is never started!
// * DEallocate sub-classes
// * stop internal engine-threads
// * FREE memory if you can
All trademarks mentioned on this page are the property of their respective owners. Engine 126.96.36.199 Copyright (c) 2017 XIA Projects 2017 Stefano Zingarini