I posted this question in another thread, but I did not get any response.
Is there any update on how to avoid this exception?
'Hover' name cannot be found in the name scope of 'System.Windows.Controls.ControlTemplate'.
I'm getting this exception. I have an unbound cell that is styled to have a button. The command handler for this button removes the corresponding dataitem from the ObservableCollection that is the datasource for the grid. Basically, it removes the row for that button. However, I get this exception when I click the button to remove the row. Adding a row works just fine.
We're doing a demo of our fancy new grid control, so any help with this would be greatly appreciated.
thanks!
FYI: I've tried other methods of deleting rows from the grid, but it has the same effect.
In the end, I found that turning off the Generic theme for the grid allowed the deletes to go through. Unfortunately, that makes the UI bit ugly. Is there a bug in that theme? Are there themes where this is not an issue?
thanks,
Kobie,
I have tested a sample with your description that has a button in cell and a custom command implemented to delete the active record corresponding to the button click. The sample uses the default theme, and I have not had an exception.
Please take the attached sample and try recreating the issue, and provide a stack trace from your application exception so I can review it.
Let me know if you have any question.
Sam
Did you try it with the Generic theme? It only happens when you turn the "Generic" them on.
Generic theme is the default theme located:
C:\Program Files\Infragistics\NetAdvantage 2010.2\WPF\DefaultStyles\DataPresenter
Can u plz tell me which service release has this fix..as i am also facing the similar issue.
Hello Tammy,
The fix was implemented in the service release 10.3.2065, and included in any service release that came out after that.
Please let us know if you incounter any issues with the latest service release. It would also be helpful to provide us with a sample to reproduce the issue if any.
Thank you,
This fix is in the 2010.3 latest service release right?
If you are getting an error with 10.3.2065 (latest service release), then please provide a sample so we can test it here to verify.
I am still getting this problem with the latest release