Jump to content
Software FX Community

CodyBarnes

Members
  • Content Count

    9
  • Joined

  • Last visited

Community Reputation

0 Neutral

About CodyBarnes

  • Rank
    Newbie
  1. Actually we have seen this bug in all versions of ChartFX that we have used including version 6.2. In fact, we first ran into this problem early last year and removed all of the wait cursors from our data view forms. Also, calling Reset is not actually necessary to cause the bug (early versions did not have a reset method). "please contact our Support Team to supportATsoftwarefx.com so this issue can be properly logged"... Isn't this your job?
  2. Service Pack applied. I still get the same error. I have build a demo app that shows this behavior, but I do not see any way to attach it to this message. The cursor is only incorrect for the plot area, not the entire chart control. Form1.cs: using System; using System.Collections.Generic; using System.ComponentModel; using System.Data; using System.Drawing; using System.Text; using System.Windows.Forms; namespace ChartCursorTest { public partial class Form1 : Form { public Form1() { InitializeComponent(); } private void Form1_Load(object sender, EventArgs e) {
  3. If the parent control cursor or the chart cursor is set (to say the wait cursor), then Chart.Reset is called, then the cursor is set back to the default, the plot area of the chart will continue to have the old cursor. this.Cursor = Cursors.WaitCursor; chart1.Reset(); //... set some other chart properties. Not necessary to reproduce bad cursor behavior chart1.Refresh(); this.Cursor = Cursors.Default;
  4. I am looking for information about the Axis.Style property. Is there a description of each of the AxisStyles available somewhere?
  5. Thank you for the quick reply Frank. This problem does indeed occur when data with only one "empty" value has been passed in. Thank you for that tip. I have fixed our application to remove that condition. My suggestion is really to do as you have noted: catch the case where the axis is empty and throw a more meaningful exception. One thing to note however is that the error is thrown outside of any of our code. If you check the call stack, you will see that the error is thrown from a paint event. ... at ChartFX.WinForms.Chart.a(PaintBar A_0, IGraphicsEx A_1) at ChartFX.WinForms.ag.a(
  6. I am also getting this error. I cannot yet produce a code snippet as that code is huge, probably unhelpful for this and above all, protected IP. A developer should however be able to check the call(s) to Math.Abs in the Axis.a function and check for any possibility that the value passed may be less than (more negative than) Int32.MinValue. In doing so, I suspect that your developer should be able to come up with a use case in which the error is generated. I have faith in your developers, they produce a quality product. StackTrace: at System.Math.AbsHelper(Int32 value) at System.Math
×
×
  • Create New...