[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-devel
Subject: mocking kcontrol infrastructure for quick kontrol module test
From: "Andriy Rysin" <arysin () gmail ! com>
Date: 2006-08-27 16:36:13
Message-ID: 3e02eb610608270936t74b39784u78955260afafda85 () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Some time ago I was able to test kcmlayout module quickly without all the
KCM infrastructure by creating a simple main.cpp file and linking it to the
module files.
The source was as simple as this:
...
int main(int argc, char *argv[])
{
QApplication app(argc, argv);
QWidget window;
KInstance* inst = new KInstance("kcmlayout");
new LayoutConfig(inst, &window);
window.show();
return app.exec();
}
Can somebody tell me how that could be done with new KGenericFactory
approach?
If I just change to LayoutConfig(window, emptyStringList) it asserts in
kcmodule.cpp
Thanks,
Andriy
[Attachment #5 (text/html)]
Some time ago I was able to test kcmlayout module quickly without all the KCM \
infrastructure by creating a simple main.cpp file and linking it to the module \
files.<br>The source was as simple as this:<br><br>...<br>int main(int argc, char \
*argv[]) <br>{<br> QApplication app(argc, \
argv);<br><br> QWidget \
window;<br><br> KInstance* inst = new \
KInstance("kcmlayout");<br> new \
LayoutConfig(inst, &window);<br><br> \
window.show();<br> return app.exec();<br>}<br><br><br>Can somebody \
tell me how that could be done with new KGenericFactory approach?<br> If I just \
change to LayoutConfig(window, emptyStringList) it asserts in \
kcmodule.cpp<br><br>Thanks,<br>Andriy<br>
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic