Hi Patrick

Your example here has helped me to get close to something I'm trying to achieve with a ListBox bound to an ObjectDataSource. The ListBox is multi-select and so SelectedIndex isn't the property I'm after. I'm trying to determine on which ListBoxItem the user displayed the context menu (after they right clicked). LeftClick is reserved for selecting and deselecting items. RightClick will open the Context Menu  - but once they've chosen the command from the ConextMenu - how can I determine which item in the Listbox they opened the ContextMenu over?

Thoughts?

I've had a look and whether or not my "thoughts" are any help depends on what you want. I have not come up with a XAML only solution and the one I have come up with is not that pretty.

1. Trap the MouseUp event on the Listbox
2. Check that e.ChangedButton == MouseButton.Right
3. Inspect the Mouse.DirectlyOver property

That will get you the Element that the mouse is over which is the case of my Listbox was the TextBlock. I did try the ContextMenu Opened and Opening events but they were no help.

HTH

Thanks Patrick. That would work too. In the end I simply moved the context menu over to the Image control instead of the ListBox - since I'm displaying a list of images inside a WrapPanel - it's the images and their source that matters to me here. I then set the CommandTarget to "{Binding RelativeSource={RelativeSource AncestorType=ContextMenu}, Path=PlacementTarget}" which gave me quick access to the Image control (and it's source). :-)

Out of curiosity - do you have any idea why WPF performance is so poor? If you use a BitMapEffect in a ListBox - rendering/painting time is very slow. I've read that this is because BitMapEffect (and others?) are currently being rendered in software? Thoughts?

Thanks for the original posting.

Tony

"WPF performance is so poor". Are you finding that performance on the whole is poor or just when using BitmapEffects. I am not suprised you find it poor with BitmapEffects. Are you repeating them in a ListBox for every item or "just" around the Listbox itself? Either way i would suggest you consider not using them.

I recommend

• Using them sparingly
• Use them on small areas such as a button
• Do NOT use them on areas that change often
• Do NOT use them on elements you are animating

Currently any object that has a BitmapEffect applied will be rendered in software. One of WPF's key benefits is making use of today's overpowered underused graphics cards so causing stuff to drop back to software rendering is not good.

"why the BitMapEffects are rendered this way..."

See the BitmapEffects docs http://msdn2.microsoft.com/en-us/library/ms743435.aspx

I don't like highlighting stuff without the context of the rest of the document so do go read it but this is the key text.

"As a special case, in WPF, effects can be set as properties on live Visual objects, such as a Button or TextBox. The pixel processing is applied and rendered at run-time. In this case, at the time of rendering, a Visual is automatically converted to its BitmapSource equivalent and is fed as input to the BitmapEffect. The output replaces the Visual object's default rendering behavior. This is why BitmapEffect objects force visuals to render in software only i.e. no hardware acceleration on visuals when effects are applied."

RadGridView and RadContextMenu: Simplifying interaction in XAML