We use cookies to give you the best experience on our website. If you continue to browse, then you agree to our privacy policy and cookie policy. (Last updated on: November 16, 2018).
Unfortunately, activation email could not send to your email. Please try again.
Syncfusion Feedback

Several issues

Thread ID:





102755 Feb 29,2012 06:57 AM UTC Mar 2,2012 12:25 PM UTC WinForms 2
Tags: Diagram
Christian Rattat
Asked On February 29, 2012 06:57 AM UTC


in some posts here you suggest to set the logical model size to "large values" when you want to have quasi unlimited drawing area.

This does work very restrictive only. First off the maximum size is obviously less than 100000 pixels. But effectively you cannot use even this because you get a lot of exceptions raised from GDI and your components when you do so.

Second as I'm visualizing processes that result into diagrams with a couple thousand connect nodes in a hierarchy the diagram size cannot be enlarged far enough to display the auto layouted hierarchy. This would require more than currently usable pixels. If it is a logical size why does it need to span a graphics window of this size (obviously)?. With these limitations the diagram control is completely useless for me. Do you plan to change this somehow (I'm using version

Third, with large diagrams the overview control does not work correctly. It displays partially only parts of the diagram (I'm detaching the diagram from the overview and connect it again as in your samples when layouting or creating the diagrams) and in some situations when you change the zoom it suddenly fits the diagram correctly. It is hardly possible to pan and zoom in the overview control with large diagrams in a senseful way. The view rectangle jumps around to arbitrary places in the overview control when you resize it by mouse.

Is there a newer version than 8.2 which solves my issues or will there be one soon? I need to take a decision quickly whether to change to a different component.


Christian Rattat
Replied On February 29, 2012 08:49 AM UTC


I just made some additional tests. When the diagram model logical width gets larger than 32000 pixels the diagram crashes when resizing to fit in the diagram's EndUpdate method. See exception call stack below. The diagram was filled with 1027 nodes each connected to one or more other in a strict hierarchy.


bei System.Drawing.Graphics.CheckErrorStatus(Int32 status)
bei System.Drawing.Graphics.DrawImage(Image image, PointF[] destPoints, RectangleF srcRect, GraphicsUnit srcUnit, ImageAttributes imageAttr, DrawImageAbort callback, Int32 callbackData)
bei System.Drawing.Graphics.DrawImage(Image image, PointF[] destPoints, RectangleF srcRect, GraphicsUnit srcUnit, ImageAttributes imageAttr)
bei Syncfusion.Windows.Forms.Diagram.LayoutGrid.DrawPoints(Graphics gfx, RectangleF rectClip)
bei Syncfusion.Windows.Forms.Diagram.LayoutGrid.DrawPointGrid(Graphics grfx, RectangleF rectGridBounds)
bei Syncfusion.Windows.Forms.Diagram.LayoutGrid.Draw(Graphics grfx, RectangleF rectGrid)
bei Syncfusion.Windows.Forms.Diagram.View.Draw(Graphics grfx, RectangleF rectClip)
bei Syncfusion.Windows.Forms.Diagram.Controls.Diagram.OnPaint(PaintEventArgs e)
bei System.Windows.Forms.Control.PaintWithErrorHandling(PaintEventArgs e, Int16 layer)
bei System.Windows.Forms.Control.WmPaint(Message& m)
bei System.Windows.Forms.Control.WndProc(Message& m)
bei Syncfusion.Windows.Forms.ScrollControl.WmPaint(Message& msg)
bei Syncfusion.Windows.Forms.ScrollControl.WndProc(Message& msg)
bei Syncfusion.Windows.Forms.Diagram.Controls.Diagram.WndProc(Message& m)
bei System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
bei System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
bei System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
bei System.Windows.Forms.SafeNativeMethods.UpdateWindow(HandleRef hWnd)
bei System.Windows.Forms.Control.Update()
bei Syncfusion.Windows.Forms.Diagram.Controls.Diagram.UpdateClientArea()
bei Syncfusion.Windows.Forms.Diagram.Controls.Diagram.OnViewOriginChanged(ViewOriginEventArgs evtArgs)
bei Syncfusion.Windows.Forms.Diagram.ViewOriginEventHandler.Invoke(ViewOriginEventArgs evtArgs)
bei Syncfusion.Windows.Forms.Diagram.ViewerEventSink.RaiseOriginChanged(ViewOriginEventArgs evtArgs)
bei Syncfusion.Windows.Forms.Diagram.View.OnOriginChanged(ViewOriginEventArgs evtArgs)
bei Syncfusion.Windows.Forms.Diagram.View.set_Origin(PointF value)
bei Syncfusion.Windows.Forms.Diagram.Controls.Diagram.UpdateOrigin(PointF ptScrollOrigin, ScrollBars scrollbars)
bei Syncfusion.Windows.Forms.Diagram.Controls.Diagram.OnVScrollBarValueChanged(Object sender, EventArgs e)
bei Syncfusion.Windows.Forms.ScrollBarWrapper.OnInnerValueChanged(Object sender, EventArgs e)
bei System.Windows.Forms.ScrollBar.OnValueChanged(EventArgs e)
bei System.Windows.Forms.ScrollBar.set_Value(Int32 value)
bei Syncfusion.Windows.Forms.ReflectScrollBar.set_Value(Int32 value)
bei Syncfusion.Windows.Forms.ScrollBarWrapper.InitScrollBar()

Amsath Ali M [Syncfusion]
Replied On March 2, 2012 12:25 PM UTC

Hi Christian,

Thanks for your interest in Syncfusion products.

Since you have created separate Direct-Trac incidents [91568 and 91565] for your query, please refer that incident for better follow up. Please let us know if you have any queries.

Amsath Ali. M


This post will be permanently deleted. Are you sure you want to continue?

Sorry, An error occured while processing your request. Please try again later.

Please sign in to access our forum

This page will automatically be redirected to the sign-in page in 10 seconds.

Warning Icon You are using an outdated version of Internet Explorer that may not display all features of this and other websites. Upgrade to Internet Explorer 8 or newer for a better experience.Close Icon