[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    mocking kcontrol infrastructure for quick kontrol module test
From:       "Andriy Rysin" <arysin () gmail ! com>
Date:       2006-08-27 16:45:40
Message-ID: 3e02eb610608270945j37e2ac4dl89c284fdf23aae6e () mail ! gmail ! com
[Download RAW message or body]

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 #3 (text/html)]

<div>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>&nbsp;&nbsp;&nbsp; \
QApplication app(argc, argv);<br><br>&nbsp;&nbsp;&nbsp; QWidget \
window;<br><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; KInstance* inst = new \
KInstance(&quot;kcmlayout&quot;);<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; new \
LayoutConfig(inst, &amp;window);<br><br>&nbsp;&nbsp;&nbsp;&nbsp; \
window.show();<br>&nbsp;&nbsp;&nbsp; return  app.exec();<br>}<br><br><br>Can somebody \
tell me how that could be done with new KGenericFactory approach?<br>&nbsp;If I just \
change to LayoutConfig(window, emptyStringList) it asserts in \
kcmodule.cpp<br><br>Thanks,<br></div>

<span>Andriy</span>



[prev in list] [next in list] [prev in thread] [next in thread]