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,
Were you able to reproduce this? We are being plagued by this error, but cannot seem to find a solution. Is this a bug? Is there a workaround? Is the only answer to stop using this theme?
Some help or a response would be greatly appreciated.
Kobie,
I have created a case (CAS-53032-674N3G) for you and logged this behavior in our issue tracking system, with an issue ID of 49130 on September 24th, and have sent you an email notification.
You will receive further updates either an automatic email, if the fix is in a form of Service Release, or I will update you when I have any more information or a workaround with regard to this issue.
Sam
Thanks. I didn't see the email notification, as it went to my spam folder.
I am experiencing similar issue could you please keep me updated on this bug
Thank You
Hello Mikhail,
I have created a separaet case for you (CAS-55196-XWLH08), and will link it to an existing issue in our issue tracking system so you receive an automatic email when a Service Release is published. If there is an alternative solution as opposed to a Service Release like a workaround I will update you occordingly.
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