What's wrong with my actions???

[jacek]

What is "this" in setupMenu()? What method you invoke "setupMenu(pMenu);" from?

[fullmetalcoder]

I have a node (the typename doesn't matter here) inheriting from QObject. It has a void contextMenuEvent(const QPoint& p) called from the view (first block of code) and the setupMenu() is also a member of this class. The puzzling thing is that I tried substituting signal/slots with QMetaObject::invokeMethod but it did not give any result either...

EDIT :
Yeah!!! I've solved it! My fix is (very) dirty but inheritance-aware as I needed and AFAIK the Trolls have no reason changing the syntax of the meta-object system before a while...
I suppose the problem comes from the fact that my nodes are created in a separate thread (to avoid GUI freeze) which gets destroyed afterward (thus no event loop is running). So I added a "QHash<QAction*, const char*> slot_table;" member which is filled in the setupMenu() method with appropriate action-method name pairs. Then, after menu execution I use the following code :

QAction *a = m.exec(p);
 
    if ( a && slot_table.contains(a) )
    {
        int idx = metaObject()->indexOfSlot(slot_table[a]);
        qt_metacall(QMetaObject::InvokeMetaMethod, idx, 0);
    }

QAction *a = m.exec(p);
    
    if ( a && slot_table.contains(a) )
    {
        int idx = metaObject()->indexOfSlot(slot_table[a]);
        qt_metacall(QMetaObject::InvokeMetaMethod, idx, 0);
    }

To copy to clipboard, switch view to plain text mode 

[jacek]

I suppose the problem comes from the fact that my nodes are created in a separate thread (to avoid GUI freeze) which gets destroyed afterward (thus no event loop is running).

If the is no event loop running in that thread, queued connections won't work.

So I added a "QHash<QAction*, const char*> slot_table;" member which is filled in the setupMenu() method with appropriate action-method name pairs.

Isn't that an equivalent of adding Qt::DirectConnection to connect statements?

[fullmetalcoder]

If the is no event loop running in that thread, queued connections won't work.

Isn't that an equivalent of adding Qt:irectConnection to connect statements?

Well, I expected my slots to be called directly but I think I now understand why they were not even if it looks strange... My nodes have been created in a given (now defunct) thread and some of their methods are called from the GUI thread. In this case created objects will be attached to the GUI thread (or am I missing something??) and it will cause Queued Connections by default which won't work properly...

[jacek]

My nodes have been created in a given (now defunct) thread and some of their methods are called from the GUI thread.

Maybe it will be enough if you simply move those objects to the GUI thread using QObject::moveToThread()?

[fullmetalcoder]

Maybe it will be enough if you simply move those objects to the GUI thread using QObject::moveToThread()?

I thought about that already but did not find any convininent way to do it in my code... Anyway I'm done now.