You can use CommandManager.InvalidateRequerySuggested ( http://msdn.microsoft.com/en-us/library/system.windows.input.commandmanager.invalidaterequerysuggested.aspx) to cause the command system to invalidate commands and update the status. This automatically happens whenever the user clicks or types anything but if changes from the back-end cause the status of commands to change you should call this method.
Hope this helps. Patrick On Tue, Oct 11, 2011 at 5:25 PM, Greg Keogh <[email protected]> wrote: > Folks, I have menus and toolbar buttons wired up to commands in the simple > textbook way. For example, I click the ‘Login’ command and my app obeys and > then I update some binding properties and I can see bound text messages > changing in response.**** > > ** ** > > However, the menu and toolbar buttons are not bound to anything, they just > use the command infrastructure (CanExecute and Execute) and they don’t > respond and change enable state. If I click a button or drop a menu down > then they “wake up” and respond and update correctly.**** > > ** ** > > Is there a way of “waking up” these commands and forcing them to update > their state when something else important happens in the app? Is it a design > fault or am I missing something?**** > > ** ** > > Greg**** > > ** ** > > _______________________________________________ > ozwpf mailing list > [email protected] > http://prdlxvm0001.codify.net/mailman/listinfo/ozwpf > >
_______________________________________________ ozwpf mailing list [email protected] http://prdlxvm0001.codify.net/mailman/listinfo/ozwpf
