QMenuBar bug for Maemo

[romulovitor]

Here's my problem. For every QMainWindow I created the following connection

QMenuBar *menu = m_window->menuBar();
connect(menu, SIGNAL(triggered(QAction*)), this, SLOT(menuTriggerAction(QAction*)));


The only problem is that not every m_window has a QAction added to it, but still the menu icon is shown on the window title. On my point of view this is a bug from 4.6 version, since it was working on the previous one.

Since I'm not sure where to post the bug, I've devided to use this forum.

Does anyone has any suggestion on how to solve this problem, since I need to add the connection for all QMainWindow that I create??

[divanov]

Here's my problem. For every QMainWindow I created the following connection
QMenuBar *menu = m_window->menuBar();
connect(menu, SIGNAL(triggered(QAction*)), this, SLOT(menuTriggerAction(QAction*)));

Is the problem really related to connecting the signal? I have doubts.

The only problem is that not every m_window has a QAction added to it, but still the menu icon is shown on the window title. On my point of view this is a bug from 4.6 version, since it was working on the previous one.

What is the relationship between the windows?

Does anyone has any suggestion on how to solve this problem, since I need to add the connection for all QMainWindow that I create??

Connecting trigerred signal to menu bars without actions makes no sense, why do you have to do that?

[romulovitor]

Is the problem really related to connecting the signal? I have doubts.

No, the problem is not connecting the signal but when "m_window->menuBar();" is invoked. Apparently once menuBar is created, the windows title show the menu icon even when it's empty

What is the relationship between the windows?

Sorry!! Not sure what you mean.

Connecting trigerred signal to menu bars without actions makes no sense, why do you have to do that?

Here's my scenario. All my QMainWindow share the same QWebView object. I first create a new QMainWindow and then render the QWebView page using Ajax ( so there's no use of loadFinished ). The page rendered by QWebView can or cannot add a QAction to the menu, however when this happen the current window has to trigger the click event.

A alternative for this approach would be to destroy and re-create this connection everytime a item is added to QMenu but I assume that this would be less efficient but would/could solve my problem.



I just added this entry here because I think that a MenuBar without QActions should not be shown on the title bar.

[divanov]

No, the problem is not connecting the signal but when "m_window->menuBar();" is invoked. Apparently once menuBar is created, the windows title show the menu icon even when it's empty

Yes, you are right, it creates new menuBar:
http://qt.gitorious.org/+qt-develope...ow.cpp#line455

Then you can use setMenuBar(0); to remove it.

[divanov]

I confirm that the bug exists in 4.6.2~git20100212-0maemo1, however this version is pretty old, an it could be fixed in the latest Qt sources available in git.
Test app:

#include <QApplication>
#include <QMainWindow>
#include <QMenuBar>
#include <QDebug>

int
main (int argc, char **argv)
{
    QApplication app(argc, argv);
    QMainWindow win;

    qDebug() << win.menuBar();
    //win.menuBar()->addAction("Action");

    win.show();

    return app.exec();
}

Menu is empty, indicator should not be visible.