masoug wrote:

Hi, I am just wondering what is so special about QActionGroup. … Does QActionGroup store action objects? -Masoug

Have you checked the docs for QActionGroup in the Qt Assistant?

If you want to remove myAction from the group, you should just use removeAction(myAction). Calling delete will “delete” myAction.

You can set a QActionGroup to be exclusive (only one action can be checked at a time). And more probably.

chetankjain wrote:

If you want to remove myAction from the group, you should just use removeAction(myAction). Calling delete will “delete” myAction.

So if I just call

Thanks!

-Masoug

masoug wrote:

So if I just call

1. delete myAction;

will I still be able to find “myAction” in “ActionGroup”? Or does “ActionGroup” have a copy of “myAction”?

Most certainly note. QActionGroups holds a pointer to myAction. When myAction is deleted, QActionGroup receives the destroyed() signal from myAction and removes it from it’s internal list.

Having said that, it’s always better/safer to call deleteLater() on QObjects:

Okay, Thanks! I got it now.

-Masoug

Oh, and by the way, why does the compiler complain about a segmentation fault when I:

That was kinda the basis of my question…

Thanks!

-Masoug

masoug, what is myAction in this case and how have it been inititalized?

Do remember that QAction is a QObject and can therefore not be copied. If you want to pass the QAction around, use pointers to the thing.

Of course myAction has to be of the type QAction *[].