Hi,
I am getting an unhandled exception when I try to resize XamNetworkNode with a GridSplitter. Attached the sample project and snapshots.
System.Reflection.TargetInvocationException occurred _HResult=-2146232828 _message=Exception has been thrown by the target of an invocation. HResult=-2146232828 IsTransient=false Message=Exception has been thrown by the target of an invocation. Source=mscorlib StackTrace: at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor) at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments) InnerException: System.ArgumentOutOfRangeException _HResult=-2146233086 _message=The parameter value must be greater than zero. HResult=-2146233086 IsTransient=false Message=The parameter value must be greater than zero. Parameter name: pixelHeight Source=PresentationCore ParamName=pixelHeight StackTrace: at System.Windows.Media.Imaging.RenderTargetBitmap..ctor(Int32 pixelWidth, Int32 pixelHeight, Double dpiX, Double dpiY, PixelFormat pixelFormat) at Infragistics.Controls.Maps.NetworkNodeNodesPanel.Render() at Infragistics.Controls.Maps.XamNetworkNode.ArrangeElements(Boolean immediate, Boolean refreshThumbnail)
I have a Grid with 3 RowDefinitions, with XamNetworkNode in 1st row, Splitter in 2nd Row & Some other control in 3rd Row. When I drag the splitter upwards trying to increase the height of row 3, I am getting an unhandled exception. It is coming when the XamNetworkNode's visible height is almost approaching zero.
Can any one please help on fixing this exception.
Thanks
Prasad
Hello,
I have been looking into this and I was able to isolate the same behavior without a splitter when the window’s height is reduced. It seems that this is related to the row height calculations e.g. if the third row’s height is set to ‘15’ rather than ‘15*’ the exception does not occur so you can try to modify the height definitions. This behavior has been logged in our tracking system with ID 206728 and the following case was created for you: CAS-164004-N5P4Y3. The next step will be for a developer to review my investigation and confirm my findings or to offer a fix, or other resolution.
The development issue 206728 has been fixed. The fix is available in the latest Service Release 15.1.20151.2188. You can download the Service Release by logging in our web site and then going to Account\My Keys and Downloads page.