How i can access my custom plugin when i loaded a ui file, my program crashed

[serjik]

Hello, i change my pro file
i have to extend ((# install)) part because my compiler was crashed,
//================================================== ==========
my test.pro file:


QT += core gui

CONFIG += uitools

#LIBS += c:/QGLabelPlugin_Release.dll

INCLUDEPATH += C:/ \
C:/TEST/test1

RESOURCES += test.qrc

SOURCES += main.cpp

#HEADERS += QGLabel.h


# install
target.path = C:/TEST/test1
sources.files = $$SOURCES $$HEADERS $$RESOURCES test.pro files
sources.path = C:/TEST/test1
INSTALLS += target sources

//================================================== ==========
main.cpp

#include <QApplication>
#include <QUiLoader>
#include <QWidget>
#include <QFile>
#include <QMainWindow>
#include <QtGui>
#include "QLabel.h"
#include "QGLabel.h"//???????????????????
//Qt 4.7.0
int main(int argc, char **argv)
{
    Q_INIT_RESOURCE(test);
 
    QApplication app(argc, argv);
 
    QUiLoader loader;
    QFile uiFile(":/test.ui");
    uiFile.open(QIODevice::ReadOnly);
    QWidget *ui = loader.load(&uiFile);
    uiFile.close();
 
    qDebug() << loader.pluginPaths();
    ui->show();
    //after loading this form i need to access its child widgets
 
QList<QGLabel*> lstLabels = ui->findChildren<QGLabel*>();////////////////////////
 
    return app.exec();
}

#include <QApplication>
#include <QUiLoader>
#include <QWidget>
#include <QFile>
#include <QMainWindow>
#include <QtGui>
#include "QLabel.h"
#include "QGLabel.h"//???????????????????
//Qt 4.7.0
int main(int argc, char **argv)
{
    Q_INIT_RESOURCE(test);

    QApplication app(argc, argv);

    QUiLoader loader;
    QFile uiFile(":/test.ui");
    uiFile.open(QIODevice::ReadOnly);
    QWidget *ui = loader.load(&uiFile);
    uiFile.close();

    qDebug() << loader.pluginPaths();
    ui->show();
    //after loading this form i need to access its child widgets

QList<QGLabel*> lstLabels = ui->findChildren<QGLabel*>();////////////////////////

    return app.exec();
}

To copy to clipboard, switch view to plain text mode 

//================================================== ==========
ERROR::::::::::::::::::::::

g++ -enable-stdcall-fixup -Wl,-enable-auto-import -Wl,-enable-runtime-pseudo-reloc -Wl,-s -mthreads -Wl -Wl,-subsystem,windows -o release\test.exe release/main.o release/qrc_test.o -L"c:\Qt\2010.05\qt\lib" -lmingw32 -lqtmain -lQtUiTools -lQtXml4 -lQtGui4 -lQtCore4

release/main.o:main.cpp.text+0x304): undefined reference to `_imp___ZN7QGLabel16staticMetaObjectE'

collect2: ld returned 1 exit status

mingw32-make[1]: Leaving directory `C:/TEST01/test-build-desktop'

mingw32-make: Leaving directory `C:/TEST01/test-build-desktop'

mingw32-make[1]: *** [release\test.exe] Error 1

mingw32-make: *** [release] Error 2

The process "C:/Qt/2010.05/mingw/bin/mingw32-make.exe" exited with code %2.
Error while building project test (target: Desktop)
When executing build step 'Make'
//================================================== ==========
thank you.

[high_flyer]

do you read the responses you get here at all?

[serjik]

Yes i read, i cant understand what can i do?

[high_flyer]

What didn't you understand from what I wrote in my last 3 posts?

what can i do?

Ask for clarification, don't just ignore.

Do you understand what using code tags means?

[SamFredericks]

release/main.o:main.cpp.text+0x304): undefined reference to `_imp___ZN7QGLabel16staticMetaObjectE'

I think the compiler finds the declaration of QGLabel, but the linker can't find the sourcecode of QGLabel, because it does not exists in your prog. But it is logic...

First, you have to create your lib - for example "qglabel". Here you have to export (Q_DECL_EXPORT) your class QGLabel. Perhaps use the template fo QtCreator. This lib you have to use in your QGLabelPlugin.
Use in your *.pro-File of your QGLabelPlugin (I think because of mingw32 different notation in LIBS...):

# where your lib is stored
LIBS += -L"c:/TEST/bin" -lqglabel
# where the header is stored
INCLUDEPATH *= C:/TEST/src

# where your lib is stored
LIBS += -L"c:/TEST/bin" -lqglabel
# where the header is stored
INCLUDEPATH *= C:/TEST/src

To copy to clipboard, switch view to plain text mode 

This lib you have to use in your Main-Prog, too, beacuse you want to use the class QGLabel.
Use in your *.pro-File of your Main-Prog:

# where your lib is stored
LIBS += -L"c:/TEST/bin" -lqglabel
# where the header is stored
INCLUDEPATH *= C:/TEST/src

# where your lib is stored
LIBS += -L"c:/TEST/bin" -lqglabel
# where the header is stored
INCLUDEPATH *= C:/TEST/src

To copy to clipboard, switch view to plain text mode 

The QUiLoader needs the Plugins of the QtDesigner, too. Because of this, you have to say the QUiLoader where your Plugin is stored.
I hope I could help a little bit.

---------------------------------------------------------------------------------------------------------
EDIT

But the implementation is in the plugin, which is loaded.

That's right. @serjik: Sorry for confusing.

[high_flyer]

I think the compiler finds the declaration of QGLabel, but the linker can't find the sourcecode of QGLabel, because it does not exists in your prog.

But the implementation is in the plugin, which is loaded.
In such a case it should be enough if he has the header for the signatures, the address of the object is loaded via the plugin, if it was not, he could not have seen an instance of his custom widget in the GUI. (which is my understanding that he does)
The instance of his custom widget is in the gui, his problem is (if I understood correctly) is that he is unable to get the instance of it.
Even if he wouldn't be able to call functions on his custom widget pointer (which i think he should in this case) he should be able to receive valid address at least.

[serjik]

Hello guys,

high_flyer: What didn't you understand from what I wrote in my last 3 posts?

OK 1)QStringList strlPaths = loader.pluginPaths (); its shoes QUiLoader available plugins paths in a QStringList .
2)QList<QGLabel*> lstLabels = ui->findChildren<QGLabel*>();
generate a QList with QGLabel class type and fill lstLabels with ui's QGLabel type CHILDREN, this is i exactly need, i need to access my ui widgets(custom plugins)

---------------------------------------------------------------------------

SamFredericks thank you for reply, i try your idea....


---------------------------------------------------------------------------
I love you Qt BUT why you have not any sample for my problem ;()

[high_flyer]

generate a QList with QGLabel class type and fill lstLabels with ui's QGLabel type CHILDREN, this is i exactly need, i need to access my ui widgets(custom plugins)

Well, do you get an empty list or not?

[serjik]

Hello high_flyer, sorry for my late,

Well, do you get an empty list or not?

yes i get an empty list, any idea?

[high_flyer]

well, either what you are reporting is incorrect, or something else is wrong.
If the list you get is empty, it means there are no QGLabel objects in your ui - but you claim you see them.
So I don't know what to tell you.

[serjik]

Dear Sir, i design a ui file with QtDesigner and i use for example Qt's standard widget same as QLabel, after loading this ui file by UiLoader, i can make a QList and accsess all this widgets, but problem is in custom widgets , when i use them and after loading ui file by UiLoader, i can see loaded custom widgets but when i try to access them by using QList<QGLabel*> lstLabels = ui->findChildren<QGLabel*>(); the list is empty,
is it possible a LIB error? or can u show a sample? PLEASE...

[high_flyer]

As I said, I can't explain the behavior your are experiencing.
Maybe someone else can help you further.

Good luck!

[high_flyer]

Are your QGLabels children of the form widget, or are they children of another widget on the forum?
If the later, you will have first to extract the parent of your QGLabels, and call findChildren() on that widget.

[serjik]

Thanks high_flyer,
I fix my problem by reading this link:
http://doc.qt.nokia.com/latest/desig...a-ui-file.html
But I didnt use UiLoader,Regards Lopez.

[high_flyer]

Would be nice if you explain what the problem was - and how you solved it - for other users that might have a similar problem.