as soon as i drag a pane in my DockManger is throws an Error
error and print screen in attachment
Hello,
Thank you for your email. I have been looking into the issue that you have described and I could not managed to reproduce it. I have created a sample application that has a XamDockManager with a XamPivotGrid in one of the ContentPane and when I drag the ContentPane, not exception is appearing. I have tested the sample application, using the RTM and the latest service release of both version 13.1 and 13.2, with the same result. I am attaching the sample application that I have created.
Would you please let me know if you can reproduce the same issue with my sample application and if not, would you please modify my sample application to show the issue, in order to be able to research what might be causing this behavior?
Looking forward to hearing from you.
Sincerely,
Krasimir, MCPD
Developer Support Supervisor - XAML
Infragistics
https://es.infragistics.com/support
updated your sample, it throws a different error. this one occurs right when the page loads instead of when i start to drag the pane
I have actually had this issue before 2012.2 and it was fixed by an SR
https://es.infragistics.com/community/forums/f/retired-products-and-controls/84172/xamgrid-in-dock-pane-causes-error
the error occurs when i drag the one that says 'Select Test' not the one with the one with the PivotGrid. the panes in the DocumentContentHost section work fine. the ones in this section fail <ig:XamDockManager.Panes>
here is my pane settings
<ig:ContentPane Header="Select Test Month" Width="180" IsFloating="False" IsPinned="True" IsMaximized="False" CloseButtonVisibility="Collapsed" WindowPositionMenuVisibility="Collapsed">
<Grid x:Name="grdFilters"
I am pretty sure it has to do with the type of content in the Contentpage
when i test this... <Grid x:Name="grdFilters" Visibility="Collapsed" ... it works fine
all that is in there is a Grid with a textblock, button, xamGrid as the Children
Also
in the post above, i recently pushed that up to 2013.2 and it is now broke as well