If you have set nodes' ContextMenu property, you could show it from PreviewKeyDown handler like this:

<diag:Diagram
	PreviewKeyDown="OnDiagramKeyDown"
	...

void OnDiagramKeyDown(object sender, KeyEventArgs e)
{
	if (e.Key == Key.System && e.SystemKey == Key.F10)
	{
		var node = diagram.ActiveItem as DiagramNode;
		if (node != null && node.ContextMenu != null)
		{
			var menu = node.ContextMenu;
			menu.PlacementTarget = node;
			menu.Placement = PlacementMode.Relative;
			menu.IsOpen = true;
			e.Handled = true;
		}
	}
} 

If you are showing it dynamically from NodeClicked event handler, you could refactor the code to call a common method from both key-down and click handlers:

void ShowContextMenu(DiagramNode node)
{
	var menu = new ContextMenu();
	var item = new MenuItem();
	item.Header = "Title";
	menu.Items.Add(item);

	menu.PlacementTarget = node;
	menu.Placement = PlacementMode.Relative;
	menu.IsOpen = true;
}

private void OnDiagramKeyDown(object sender, KeyEventArgs e)
{
	if (e.Key == Key.System && e.SystemKey == Key.F10)
	{
		var node = diagram.ActiveItem as DiagramNode;
		if (node != null)
		{
			ShowContextMenu(node);
			e.Handled = true;
		}
	}
}

private void OnNodeClicked(object sender, NodeEventArgs e)
{
	if (e.MouseButton == MouseButton.Right)
	{
		ShowContextMenu(e.Node);
		return;
	}
} 

I hope that helps,
Stoyan

Do you mean getting some built-in support for all points from Software Applications section of 508 standard (http://www.section508.gov/section-508-standards-guide#Software), or just showing context menu using keyboard shortcut?

We've added built-in binding to ApplicationCommands.ContextMenu in this v3.3 build:

https://mindfusion.eu/_beta/wpfdiag33.zip

That command is executed for both Shift+F10 and the dedicated menu key. It will show Diagram.ActiveItem.ContextMenu if it's not null. If you do not set items' ContextMenu properties but show menus dynamically as in second example above, you will have to add your own binding to the command.

We'll have in mind the other points from 508 for next releases.

I hope that helps,
Stoyan

You will need to add a test for the Key.Apps key too:

// PreviewKeyUp="OnDiagramKeyUp" in Xaml
private void OnDiagramKeyUp(object sender, KeyEventArgs e)
{
	if (e.Key == Key.Apps)
	{
		var node = diagram.ActiveItem as DiagramNode;
		if (node != null)
		{
			ShowContextMenu(node);
			e.Handled = true;
		}
	}
}

// PreviewKeyDown="OnDiagramKeyDown" in Xaml
void OnDiagramKeyDown(object sender, KeyEventArgs e)
{
	if (e.Key == Key.System && e.SystemKey == Key.F10)
	{
		var node = diagram.ActiveItem as DiagramNode;
		if (node != null)
		{
			ShowContextMenu(node);
			e.Handled = true;
		}
	}
} 

I had to move the Key.Apps case to a KeyUp handler because of this problem:
http://stackoverflow.com/questions/4333032/context-menu-disappears-when-opened-w...

I hope that helps,
Stoyan

Hi,

v3.3 is now in beta tests (http://mindfusion.eu/Forum/YaBB.pl?num=1427803969). This version no longer requires design-time licensing so you can remove the respective line from licenses.licx if you are getting errors from LC.exe.

I hope that helps,
Stoyan

We've omitted scripting.dll from last beta upload. Now you can find it with new build here:
https://mindfusion.eu/_beta/wpfdiag33.zip

I hope that helps,
Stoyan

That looks like a bug in WPF context menus. The keyboard focus is on the context menu when KeyUp event is raised for Apps key. The menu closes even if it was shown from WPF's own ApplicationCommand.ContextMenu, so the decision to close it comes from the framework code. You can work around this by stopping event propagation from PreviewKeyUp:

nodeCtxMenu.PreviewKeyUp += (sender, e) => e.Handled = e.Key == Key.Apps;

I hope that helps,
Stoyan