Problem with QDialog , its not closeing right away when pressing the x , how to make it NOT on top?

goetz

It's all explained in the [[Doc:QDialog]] API docs, including examples (look for the modal/modeless explanations), did you check those already?

umen242

Ok Thanks about the modeless problem i understood .
what about the connect / disconnect problem am i doing it right

goetz

[quote author="umen242" date="1312788672"]Ok Thanks about the modeless problem i understood .
what about the connect / disconnect problem am i doing it right [/quote]

Probably not. The code looks a bit weird to me. But it's hard to analyze without the complete classes and without knowing what you actually want to do.

umen242

what do you what me to show you , its context menu (right click ) when im on tree node it give me the option to right click and opem QDialog window

goetz

So, why do you double the functionality? The signal mapper is only needed if the context menu needs to stay open during the execution of the slot called from the mapper.

The menu exec gives you back the selected menu entry:

@
QAction* selectedItem = ContextMenu.exec(globalPos);
@

Just call the appropriate dialog according to the action returned by exec and abandon the QSignalMapper completely.

umen242

im using the mapper to pass value to OpenWin slot when triggered() signal is invoked
i don't see any other option

goetz

Try this:

@
void MainWindowContainer::ShowContextMenu(const QPoint& pos) // this is a slot
{
QPoint globalPos = ui.treeView_mainwindow->mapToGlobal(pos);
QAction* selectedItem = ContextMenu.exec(globalPos);

if(selectedItem == OpenAction) {
    // do the open stuff
} else if(selectedItem == EditAction) {
    // do the edit stuff
}

}
@

Problem with your approach is, that the actions fire while the menu is open - and during this time, the menu's event loop (call of exec) is still running and may interfere with the rest of the application.

umen242

Thanks Allot for your time to answer.
but what if i have only one Action in the Context menu , and the action will be by the parameter taken from the node it stand on

goetz

Then you will have some code that attaches the data to the action anyways.

You could consider "dynamic properties":http://doc.qt.nokia.com/4.7/qobject.html#dynamic-properties attached to your QAction instances. You can read those from the returned QAction.

umen242

ok i will check it out ,thanks again