PopupButton

Owen,

The problem here seems to be our feature where PopupButton tries to disable itself if all the contained menu items are disabled. What happens is that it is checking whether the menu items (buttons) are enabled. Since they have commands but there are no command bindings set up at the time of checking, they are disabled. The Window.Load event then fires, adding the bindings, but nothing tells the buttons to update the parent popup button.

A workaround for this issue is to move your bindings setup code to the constructor after InitializeComponent. Everything works then.

Alternatively you can turn off the auto-disable feature by setting PopupButton.AutoDisableWhenPopupContentIsDisabled = false.

We have a multiple view interface (in tabs specifically) and with the way routed commands work in WPF, any commands that are used in more than one view will also be executed even if the view is no currently the "active" one, so we have to register and unregister commands/commandbindings on the fly as views are shown and hidden. I've tried CommandManager.InalidateRequerySuggested() after the view state changes but to no avail.

In the short term we've simply created another command and OR'ed together the results of the can executes from the pertinent button commands.

Is there another solution to this?


[Modified at 09/16/2009 11:41 AM]

The other thing we did for another customer who has disabling issues was have PopupButton support a Command of its own. So you can make a command just to determine if the PopupButton should be disabled or not, based on whether the command can execute. That would probably work for you too here.

Kris,

Please see our reply here:
http://www.actiprosoftware.com/Support/Forums/ViewForumTopic.aspx?ForumTopicID=4289