Change row selection on right-click

[Brad]

I am using a context menu that gets loaded in the "CellLoaded" event for some cells (i.e. I want the context menu in some columns, but not in others).  I have this working beautifully except for one minor problem.  When the user right-clicks the cell, the row selection doesn't change.  So, if I right-click a cell that is not in the active row, the context menu is for a cell that is in an unselected row.  The visual of this is not satisfactory to the client.  "IsSynchronizedWithCurrentItem" works great for left-clicks, but doesn't seem to have any effect for right-clicks.  Is there an easy way to fix this so that if I right-click on a cell, the row selection changes to match?

I've been trying to do this using the grid's "ContextMenuOpening" event, but there doesn't seem to be enough information available in the arguments to tell me which row was clicked on.

Any help would be much-appreciated.

Thanks!

Brad.

[Stefan]

Hi Brad,

In order to select an item on right mouse button click, you can hook up to the MouseRightButtonUp event of the control and set the IsSelected property of the given row to True. The approach is discussed in greater detail in the Select row with right mouse click forum thread. Can you please take a look at it?

Regards,
Stefan
Progress Telerik

[Brad]

Sorry for my slow reply - I was out of town.

OK, I got it working that way, though I'm not crazy about how it's implemented.  I'm using MVVM and, whereas that thread refers to MVVM, it doesn't actually solve it using MVVM - the MVVM part of the thread dies.  For example, it says use "MouseRightButtonUp instead ItemClick of the menu".  Well, 1) that's for Silverlight, and 2) neither of those is really MVVM unless I can bind a command to them.

 

Thanks!

Brad.

[Stefan]

Hello Brad,

Thanks for the update.

Indeed, the demo referred in the forum thread is for Silverlight, but the implementation demonstrated in it is applicable for WPF as well. We actually have the same Row Context Menu WPF Demo. Since you are not convenient with the approach of using an attached behavior, you can consider utilizing the EventToCommandBehavior mechanism. Can you please take a look at it?

Regards,
Stefan
Progress Telerik