Commands in Application Menu

Hi Tore,

Could you please put together a sample project that reproduces the issue you are seeing. It is hard to determine what the problem is from just your description.

Actually, a sample project of the system would be hard, as it is really big, I can however sum up the dilemma:

I got an application menu with several buttons, they are linked to commands, for example:

<ribbon:Button x:Name="ribbonAppMenuFooterButtonsOptionsBtn" Command="recourcesFiles:LydiaCommands.ShowOptions"
FontSize="11" Padding="0" Height="23" Foreground="DarkBlue" FontWeight="Normal"/>

This button is the options button, which is among the buttons disabled. In my main window the commandbinding looks like this:

<CommandBinding Command="recourcesFiles:LydiaCommands.ShowOptions" Executed="ShowOptions_Executed" CanExecute="LydiaCommand_Always_CanExecute" />

The CanExecute simple just consists of this:
private void LydiaCommand_Always_CanExecute(object sender, CanExecuteRoutedEventArgs e)
{
e.CanExecute = true;
}

The problem now is the following, I use Actipro Navigation also. When I click on one of my modules directly without "touching" the main GUI, I somehow seem to not be able to get the command activated. The problem dissapears when I click physically on the navigationbutton. I want to fix this programatically, such that users don't get buttons in the Application Menu disabled.

I have tried the following:
a) Trying CommandManager's static method for invalidate commands.
b) Trying to set the focus programatically.
c) Trying setting CommandTarget.
d) Trying to set focus on the Main Window programatically.

Have you got other suggestions for this problem? The problem I think is simple for those akin to commands, ribboncommands, CanExecute and WPF, if you got a solution I would be very glad.

Tore Aurstad,
Developer at Lydia FM
Norway

Is the NavigationBar hosted in a separate window? I'm not exactly sure what you mean by the "main GUI" and "modules", and don't know how they are connected.

You may want to read the Commanding Overview (external link to MSDN) topic.

I can tell you is that since you do not specify the CommandTarget (the element on which the command is executed), the element with keyboard focus will be used as the command target. So in this case, if the associated command would always be handled by the window, then maybe you would want to set that as the command target. But again, this depends on your setup.

You said you tried this in item (c) above, but how did you set the CommandTarget?

Everything is in the same window, I tried setting the command target to main window.
I will look at the link provided, "Commanding Overview", I have read some of it previous. I will also look up RoutedEvents, and notify you if I find a solution.

Is the Navigationbar buttons sending events up the tree? If they are set to e.Handled automatically, the Window will not receive CanExecuteChanged Events for instance?

Tore Aurstad,
Developer, Lydia Facility Management,
Norway.

The NavigationBar only handles the commands defined in the NavigationCommands class, all of which are specifically created for the NavigationBar.

If you can email some additional information or source to our support address, then we can take a look. We'd love to help you resolve this, but with the limited information it is difficult.

Hi,

I am also facing the same problem and really appreciate if you can post the solution.

Thanks,
Anurodh