Quote Originally Posted by MarekR22 View Post
Apparently you are misunderstanding something. After you add action to some object you shouldn't control this object, don't change it: enable state, title, icon and so on.
All this state changes should be done by QAction. Note that not all buttons are handling QActions, QToolButton does.
The menu bar item is a QAction though, and completely separate from the button. The Button and the QAction both had the same effect on the simulator side, but from Qt they send out different signals (although they shouldn't and won't when I do similar things in the future- see below). My point is that QAction.setEnabled(false) doesn't seem to be working. If I delete the button completely and just have the QAction menu item, it still doesn't work.

Quote Originally Posted by wysota View Post
If you want an action and a button to do the same thing then replace your QPushButton instance with QToolButton and use QToolButton::setDefaultAction() passing it the action from the menu. Then the menu entry and the button will always be synchronized when you disable or otherwise change properties of the action object.
Yea that makes sense- I knew that and had just forgotten. I'm still learning all the ins and outs of Qt so sometimes things get forgotten .