Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

I can not get methods from QMetaObject, methods offset and count are equals

Tags:

c++

qt

metaobject

i have a class that inherits from QObject and have the Q_OBJECT macro:

class SomeClass: public QObject
{
    Q_OBJECT
public:
    SomeClass(QObject *parent = 0);
    void method1();
    void method2();
    ...
};

in another class in the same header i create an instance of that class, and then i try to get all Methods from 'SomeClass' and store it in a QMap:

this->someclass = new SomeClass(); // in constructor.

...

cout<<"init some class methods"<<endl;
    const QMetaObject *metaobj = dynamic_cast<QObject*>(this->someclass)->metaObject();
    cout<<"offset "<<metaobj->methodOffset()<<endl;
    for(int i = metaobj->methodOffset();i < metaobj->methodCount();i++){
        QMetaMethod metamethod = metaobj->method(i);
        //if(metamethod.methodType() == QMetaMethod::Method){
            QString methodname = QString(metamethod.signature());
            methodname = methodname.replace(QRegExp("\\(.*\\)"),"");
            controlmethods.insert(methodname,metamethod);
            cout<<"added method: "<<metamethod.signature()<<" as "<<methodname.toAscii().data()<<endl;
        //}
    }

But this do not showed me any method added because the methods offset is equals to the methods count, why can be? i dont get with the reason, Thanks any help.

like image 821
Diego Fernando Murillo Valenci Avatar asked Jan 29 '13 05:01

Diego Fernando Murillo Valenci


2 Answers

You need to use the Q_INVOKABLE macro for each method you want to see in the QMetaObject.

From the documentation:

Q_INVOKABLE

Apply this macro to declarations of member functions to allow them to be invoked via the meta-object system. The macro is written before the return type, as shown in the following example:

class Window : public QWidget {
    Q_OBJECT

public:
    Window();
    void normalMethod();
    Q_INVOKABLE void invokableMethod(); };

The invokableMethod() function is marked up using Q_INVOKABLE, causing it to be registered with the meta-object system and enabling it to be invoked using QMetaObject::invokeMethod(). Since normalMethod() function is not registered in this way, it cannot be invoked using QMetaObject::invokeMethod().

You can also use the slots macro. I think Q_INVOKABLE may be more minimal, though.

QMetaObject is only aware of signals, slots, properties and other invokable member functions, occasionally referred to as "meta-methods" as a group.


Also, for the first line of your example, you should (probably) just call

const QMetaObject *metaobj = someClass->metaObject();

This isn't just cosmetic. The dynamic_cast would move type-checking to runtime, which isn't necessary if you know at compile time that someClass is a pointer to a QObject-derived class. (dynamic_casting to QObject* will work, and will get you the correct QMetaObject because of virtual inheritance, but it's unnecessary, less safe, and unclear.)

You don't actually need an instance of the class to get the meta-object:

const QMetaObject *metaobj = SomeClass::staticMetaObject();

This is possible because there is one QMetaObject per class, not per object.

For anyone who wants to know more about the meta-object system, I recommend coffee and the documentation. Usually you don't need to deal with QMetaObject instances directly, unless you're writing a scripting engine or something equally 'meta'. It's easy to unintentionally duplicate functionality Qt already provides.


Also, Q_DECLARE_METATYPE is not what you want.

like image 133
typelist Avatar answered Oct 16 '22 11:10

typelist


There is some kind of ambiguity in the official docs.

First we see:

method() and methodCount() provide information about a class's meta-methods (signals, slots and other invokable member functions).

But later:

int QMetaObject::methodCount() const Returns the number of methods in this class, including the number of properties provided by each base class. These include signals and slots as well as normal member functions.

But actually we can't have access to 'normal' methods through Qt MetaObject System.

So, to get access to your methods, you should declare them with the Q_INVOKABLE macro:

Q_INVOKABLE void method1();
Q_INVOKABLE void method2();
like image 39
hank Avatar answered Oct 16 '22 10:10

hank