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.
Kindly provide me the service release details. I have installed NetAdvantage for .NET 2010 Vol. 2 (WPF4 2045)
There is only one service release available at a release period per product version. Currently, the available service release for NetAdvantage for WPF 10.2. is 20102.2139. This will not be available in public after the next service release is published; however; in case you need any previous service release for some reason, we can make an internal request, and send you the link to download it.
Let me know if you have any question.
I am also having this same problem with the NetAdvantage 10.3 WPF xamDataGrid control. Is this fix not part of the v3 controls? What do I need to do to fix it? This is a highly frustrating error since it doesn't appear to even be trappable.
This issue has been fixed. You would need to install the latest service release, I mentioned in the previous post.
I have encountered the same issue in WPF Controls 10.3. In order to reproduce it create a XamDataGrid and bind it to an observable list of objects. It is important that the Theme is set to "Generic". Put somewhere above it a menu and add to the Menu a MenuItem that would delete a row from the datasource of the grid and make it so that the placement of the menu item is somewhere overlapping the row that would be removed. Now click on the MenuItem, making sure your mouse is above both menu item and the grid row that is removed. An error 'Hover' name cannot be found in the name scope of 'System.Windows.Controls.ControlTemplate' will be fired. In order to see that this is indeed the root of the problem, try clicking on the menuitem in such a way that the mouse is not over the grid row. The error does not appear.
Also, I would like to point out that we have removed the entire control template and replaced it with our own by removing the 'Hover' Border and any storyboard associated with it. The error STILL appears. We used Snoop to make sure the border is indeed gone and that the trigger is removed and that the template does not have the storyboards associated with the hovering and they where.
I have tried to reproduce the error using normal WPF controls, but failed. I believe it is somewhat linked to the Infragistics template caching mechanism. I can find no local solution, since the template that is throwing the error is not the template of the grid! I don't know how I can access this phantom template.
I'm getting this issue too but it happens when I'm trying to enter data in the filter row.
Kindly provide me the link to download the same.
Here is how to download the latest service release:
Login to your Infragistics account.- Click on 'My IG' - Click on 'NetAdvantage' tab.- Select the appropriate link corresponding to the version you have installed, in this case 10.3.- Click on the 'Service Release' (color coded item) and download it.
Is there any default template for 'DataRecordCellArea'. I tried finding it at "Program Files\Infragistics\NetAdvantage 2010.2\WPF\DefaultStyles" but not sure if there is any..
Please use a new thread or a different thread if your question is unrelated to this post.
DataRecordCellArea is located in the DefaultStyle folder you have mentioned. Look in the DataPresenter folder inside for DataPresenterGeneric_Express.xaml.
I am still getting this problem with the latest release
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.
This fix is in the 2010.3 latest service release right?
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.