Properties Dialog Issues...

[User (Legacy)]

We are having stability issues with the properties dialog in our 

application.

When we open the properties dialog and change certain properties (i.e. turn 

on interlaced for the Yaxis) we can Overflow errors similar to the ones 

shown below.

Strangely, if we righ click on the yaxis and select "interaced" from the 

popup menu it works fine.

This situation happens with more than just the interlaced property. 

Sometimes it is min, & max for an axis, sometimes it is 3d properties.

We have also found that our charts frequently go blank "no bars/lines/etc." 

when we change numeric format of the axis and or decimal points.  We noticed 

strange things happening with the min and max in debug mode, so we added a 

"recalc scale" on severalof the events which seemed to help reduce the 

number of blank charts. These "recalc scale calls" have not helped with the 

attached errors however.

1. Have you seen anything like this before? If yes, is there a solution?

2. If not, what additional info do you need from us to debug?

3. If you have any advice on the best events to place our reclac scale code 

to ensure that we reduce the number of blank charts, that would be 

appreciated as well.

Thanks in advance for your help.

[Software FX]

> 1. Have you seen anything like this before? If yes, is there a solution?

No. We are not aware of any issues with the properties dialog that will 

cause an exception.

> 2. If not, what additional info do you need from us to debug?

Please export the chart to a binary file, using the Export method, before 

opening the properties dialog and attach it to your posting along with the 

exact steps to follow to reproduce the problem from the moment the chart is 

exported.

> 3. If you have any advice on the best events to place our reclac scale 

> code to ensure that we reduce the number of blank charts, that would be 

> appreciated as well.

Black charts are produces when the scale ends up empty. You can check for 

this condition:

if (chart.AxisY.Max <= chart.AxisY.Min)

    chart.RecalcScale();

Whenever the property dialog´s ok or apply button is pressed, you will 

receive an InternalCommand event, the command id will be CommandId.Apply.

-- 

Francisco Padron

www.chartfx.com

[User (Legacy)]

Attached is one example of a chart that is giving us problems with the 

properties dialog.

If we open this chart then...

1. Righ click the chart, select properties.

2. Goto YAxis

3. Change the decimal points to 1

4. Hit apply or OK

Crash

If we open this chart then...

1. Righ click the chart, select properties.

2. Goto YAxis

3. Check of Interlaced

4. Hit apply or OK

Crash

We get the errors regardless of whether the chart has one or two y axses. 

There are also several other combinations of propeties that will cause the 

errors.

Thanks for your help.

Aside:

Notice that we also get unusual results with one of the series being plotted 

off the righ side of the chart.

"SoftwareFX Support" <noreply@softwarefx.com> wrote in message 

news:KTM56kc0GHA.3604@webserver3.softwarefx.com...

>> 1. Have you seen anything like this before? If yes, is there a solution?

>

> No. We are not aware of any issues with the properties dialog that will

> cause an exception.

>

>> 2. If not, what additional info do you need from us to debug?

>

> Please export the chart to a binary file, using the Export method, before

> opening the properties dialog and attach it to your posting along with the

> exact steps to follow to reproduce the problem from the moment the chart 

> is

> exported.

>

>> 3. If you have any advice on the best events to place our reclac scale

>> code to ensure that we reduce the number of blank charts, that would be

>> appreciated as well.

>

> Black charts are produces when the scale ends up empty. You can check for

> this condition:

>

> if (chart.AxisY.Max <= chart.AxisY.Min)

>    chart.RecalcScale();

>

> Whenever the property dialog´s ok or apply button is pressed, you will

> receive an InternalCommand event, the command id will be CommandId.Apply.

>

> -- 

> Francisco Padron

> www.chartfx.com

>

>

[User (Legacy)]

I just wanted to make sure I posted my previous example correctly and that 

you were able to receive my binary file successfully.

Thanks.

"jimmy" <rup207@aol.com> wrote in message 

news:gNFrwmp0GHA.3960@webserver3.softwarefx.com...

>

> Attached is one example of a chart that is giving us problems with the 

> properties dialog.

>

> If we open this chart then...

>

> 1. Righ click the chart, select properties.

> 2. Goto YAxis

> 3. Change the decimal points to 1

> 4. Hit apply or OK

>

> Crash

>

> If we open this chart then...

>

> 1. Righ click the chart, select properties.

> 2. Goto YAxis

> 3. Check of Interlaced

> 4. Hit apply or OK

>

> Crash

>

> We get the errors regardless of whether the chart has one or two y axses. 

> There are also several other combinations of propeties that will cause the 

> errors.

>

> Thanks for your help.

>

>

> Aside:

>

> Notice that we also get unusual results with one of the series being 

> plotted off the righ side of the chart.

>

>

>

>

> "SoftwareFX Support" <noreply@softwarefx.com> wrote in message 

> news:KTM56kc0GHA.3604@webserver3.softwarefx.com...

>>> 1. Have you seen anything like this before? If yes, is there a solution?

>>

>> No. We are not aware of any issues with the properties dialog that will

>> cause an exception.

>>

>>> 2. If not, what additional info do you need from us to debug?

>>

>> Please export the chart to a binary file, using the Export method, before

>> opening the properties dialog and attach it to your posting along with 

>> the

>> exact steps to follow to reproduce the problem from the moment the chart 

>> is

>> exported.

>>

>>> 3. If you have any advice on the best events to place our reclac scale

>>> code to ensure that we reduce the number of blank charts, that would be

>>> appreciated as well.

>>

>> Black charts are produces when the scale ends up empty. You can check for

>> this condition:

>>

>> if (chart.AxisY.Max <= chart.AxisY.Min)

>>    chart.RecalcScale();

>>

>> Whenever the property dialog´s ok or apply button is pressed, you will

>> receive an InternalCommand event, the command id will be CommandId.Apply.

>>

>> -- 

>> Francisco Padron

>> www.chartfx.com

>>

>>

>

>

>

[Software FX]

Please download the latest Service Pack. This problem has been fixed.

> Notice that we also get unusual results with one of the series being 

> plotted off the righ side of the chart.

This is caused by an incorrect set-up of your chart properties. Your main 

gallery (AllSeries.Gallery is Lines, which supports X-Values) but you also 

have some series as bars. This combination is only permitted IF the X-Axis 

is categorical.

To fix this, set chart.AllSeries.Gallery = Gallery.Bar prior to setting each 

individual series gallery.

-- 

Francisco Padron

www.chartfx.com

[User (Legacy)]

I have this same issue with the properties dialog crashing the application 

and I have the latest update.  For example, I just changed the Decimals 

field under Y Axis to 1 and hit Apply, once the chart updated I changed it 

again to 0 and hit apply.  At this point the program crashes. with the 

following exception and stack trace.

Just FYI, I am using the graph to plot 3 series with 2 seperate Y axes.

Exception:

+  [system.OverflowException] {"Overflow error."} System.OverflowException

Stack trace:

at System.Drawing.Graphics.CheckErrorStatus(Int32 status)

at System.Drawing.Graphics.DrawLine(Pen pen, Int32 x1, Int32 y1, Int32 x2, 

Int32 y2)

at ChartFX.WinForms.Internal.GraphicsEx.DrawLine(Pen pen, Int32 x, Int32 y, 

Int32 x2, Int32 y2)

at ChartFX.WinForms.Galleries.Line.a(PaintMarkBase A_0, Int32 A_1, Int32 

A_2, Int32 A_3, Int32 A_4, Int32 A_5)

at ChartFX.WinForms.Galleries.Line.a(PaintMarkBase A_0, Int32 A_1, Int32 

A_2, Int32 A_3, Int32 A_4)

at ChartFX.WinForms.Galleries.Line.a(Int32 A_0, PaintMarkBase A_1, Int32& 

A_2, Int32& A_3)

at ChartFX.WinForms.aw.a(Int32& A_0, Int32& A_1)

at ChartFX.WinForms.aw.b(Int32& A_0, Int32& A_1)

at ChartFX.WinForms.aw.t()

at ChartFX.WinForms.aw.a(IFrame A_0, Int32& A_1)

at ChartFX.WinForms.Chart.a(PaintBar A_0, IGraphicsEx A_1)

at ChartFX.WinForms.ag.a(PaintEventArgs A_0)

at System.Windows.Forms.Control.PaintWithErrorHandling(PaintEventArgs e, 

Int16 layer, Boolean disposeEventArgs)

at System.Windows.Forms.Control.WmPaint(Message& m)

at System.Windows.Forms.Control.WndProc(Message& m)

at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)

at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)

at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr hWnd, Int32 

msg, IntPtr wparam, IntPtr lparam)

at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)

at 

System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(Int32 

dwComponentID, Int32 reason, Int32 pvLoopData)

at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 

reason, ApplicationContext context)

at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 

reason, ApplicationContext context)

at System.Windows.Forms.Form.ShowDialog(IWin32Window owner)

at System.Windows.Forms.Form.ShowDialog()

at ChartFX.WinForms.Internal.UI.g.a(Object A_0, Object A_1, IUIObject A_2, 

Int32 A_3, ResourceSet A_4)

at ChartFX.WinForms.Chart.ShowPropertiesDialog(Object context, Int32 

pageNumber)

at ChartFX.WinForms.ba.a(CommandsEventArgs A_0, Boolean& A_1)

at ChartFX.WinForms.ba.a(Object A_0, CommandsEventArgs A_1, Boolean& A_2)

at ChartFX.WinForms.ba.a(Object A_0, CommandsEventArgs A_1)

at ChartFX.WinForms.CommandCollection.a(Int32 A_0, Int32 A_1, IUIObject A_2)

at ChartFX.WinForms.CommandCollection.a(Object A_0, Int32 A_1, ICommand A_2, 

Boolean A_3, IUIObject A_4)

at ChartFX.WinForms.a0.a(EventArgs A_0)

at System.Windows.Forms.MenuItem.MenuItemData.Execute()

at System.Windows.Forms.Command.Invoke()

at System.Windows.Forms.Command.DispatchID(Int32 id)

at System.Windows.Forms.Control.WmCommand(Message& m)

at System.Windows.Forms.Control.WndProc(Message& m)

at ChartFX.WinForms.ai.a(Message& A_0)

at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)

at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)

at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr hWnd, Int32 

msg, IntPtr wparam, IntPtr lparam)

at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)

at 

System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(Int32 

dwComponentID, Int32 reason, Int32 pvLoopData)

at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 

reason, ApplicationContext context)

at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 

reason, ApplicationContext context)

at System.Windows.Forms.Application.Run(Form mainForm)

at WPM2_Test.Program.Main() in C:\Work\iMonitoring\PC\NET 

versions\WPM2_Test\WPM2_Test\Program.cs:line 17

at System.AppDomain.nExecuteAssembly(Assembly assembly, String[] args)

at System.AppDomain.ExecuteAssembly(String assemblyFile, Evidence 

assemblySecurity, String[] args)

at Microsoft.VisualStudio.HostingProcess.HostProc.RunUsersAssembly()

at System.Threading.ThreadHelper.ThreadStart_Context(Object state)

at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, 

ContextCallback callback, Object state)

at System.Threading.ThreadHelper.ThreadStart()

"SoftwareFX Support" <noreply@softwarefx.com> wrote in message 

news:qkaNjND2GHA.1856@webserver3.softwarefx.com...

> Please download the latest Service Pack. This problem has been fixed.

>

>> Notice that we also get unusual results with one of the series being 

>> plotted off the righ side of the chart.

>

> This is caused by an incorrect set-up of your chart properties. Your main 

> gallery (AllSeries.Gallery is Lines, which supports X-Values) but you also 

> have some series as bars. This combination is only permitted IF the X-Axis 

> is categorical.

>

> To fix this, set chart.AllSeries.Gallery = Gallery.Bar prior to setting 

> each individual series gallery.

>

>

> -- 

> Francisco Padron

> www.chartfx.com

>

[Software FX]

We are unable to reproduce the problem using the latest Service Pack.

Can you please provide step-by-step instructions on how to reproduce it 

starting from a default chart.

-- 

Francisco Padron

www.chartfx.com