Cursor

[CodyBarnes]

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; 

[maximop]

Unable to replicate. Make sure that you are running the latest service pack:

http://support.softwarefx.com/ShowInteractive.aspx?Product=CfxNet62&option=0

[CodyBarnes]

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)
  {
this.Cursor = Cursors.WaitCursor;
chart1.Reset();
chart1.Refresh();
this.Cursor = Cursors.Default;
  }
}
}

 

 

Form1.Designer.cs

namespace ChartCursorTest
{
partial class Form1
{
  /// <summary>
  /// Required designer variable.
  /// </summary>
  private System.ComponentModel.IContainer components = null;

  /// <summary>
  /// Clean up any resources being used.
  /// </summary>
  /// <param name="disposing">true if managed resources should be disposed; otherwise, false.</param>
  protected override void Dispose(bool disposing)
  {
if (disposing && (components != null))
{
  components.Dispose();
}
base.Dispose(disposing);
  }

  #region Windows Form Designer generated code

  /// <summary>
  /// Required method for Designer support - do not modify
  /// the contents of this method with the code editor.
  /// </summary>
  private void InitializeComponent()
  {
this.chart1 = new ChartFX.WinForms.Chart();
((System.ComponentModel.ISupportInitialize)(this.chart1)).BeginInit();
this.SuspendLayout();
//
// chart1
//
this.chart1.Dock = System.Windows.Forms.DockStyle.Fill;
this.chart1.Location = new System.Drawing.Point(0, 0);
this.chart1.Name = "chart1";
this.chart1.Size = new System.Drawing.Size(292, 271);
this.chart1.TabIndex = 0;
//
// Form1
//
this.AutoScaleDimensions = new System.Drawing.SizeF(6F, 13F);
this.AutoScaleMode = System.Windows.Forms.AutoScaleMode.Font;
this.ClientSize = new System.Drawing.Size(292, 271);
this.Controls.Add(this.chart1);
this.Name = "Form1";
this.Text = "Form1";
this.Load += new System.EventHandler(this.Form1_Load);
((System.ComponentModel.ISupportInitialize)(this.chart1)).EndInit();
this.ResumeLayout(false);
this.PerformLayout();

  }

  #endregion

  private ChartFX.WinForms.Chart chart1;
}
}

 

 

 

 

 

 

[maximop]

I was finally able to replicate the problem; originally, I had tested this under ChartFX for .NET 6.2 since this was the discussion group you post it your thread under but the problem is specific to ChartFX 7. In the future, to expedite your request(s), please ensure that you post your questions/issues under the correct group. Furthermore, this seems to be very specific to calling the Reset() method before changing the Cursor again so this may be very with low priority.

In any case, please contact our Support Team to supportATsoftwarefx.com so this issue can be properly logged and so you can be notified once this problem is solved.

[CodyBarnes]

 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?

[maximop]

The reason why you need to contact Support at that e-mail is so an incident # can be generated and assigned to you so when this bug is fixed, we are able to notify you.