Steema Issues Database

Note: This database is for bugs and wishes only. For technical support help, if you are a customer please visit our online forums;
otherwise you can use StackOverflow.
Before using this bug-tracker we recommend a look at this document, Steema Bug Fixing Policy.



Bug 1157 - Caching impeding designtime changes when modifying gardient direction in Bar fill gradients
Summary: Caching impeding designtime changes when modifying gardient direction in Bar ...
Status: RESOLVED FIXED
Alias: None
Product: .NET TeeChart
Classification: Unclassified
Component: Chart (show other bugs)
Version: unspecified
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Steema Issue Manager
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-03-03 05:51 EST by marc meumann
Modified: 2015-03-03 09:56 EST (History)
1 user (show)

See Also:
Chart Series: ---
Delphi / C++ Builder RAD IDE Version:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description marc meumann 2015-03-03 05:51:13 EST 
Making changes to a Barseries' fill gradient (eg. Direction) isn't showing up at designtime when making those changes with the editor.

Workaround:
Disabling cache resolves the issue.
ie. Steema.TeeChart.Utils.UseCaches = false;
Comment 1 christopher ireland 2015-03-03 09:31:46 EST 
The following code works as expected with UseCaches either true or false:

    Bar series = new Bar();

    private void InitializeChart()
    {
      tChart1.Aspect.View3D = false;
      tChart1.Series.Add(series);
      series.FillSampleValues();

      series.Gradient.Visible = true;
      //Utils.UseCaches = false;
      EditorUtils.FillEnum(comboBox1, typeof(LinearGradientMode));
    }

    private void comboBox1_SelectedIndexChanged(object sender, EventArgs e)
    {
      series.Gradient.Direction = (LinearGradientMode)comboBox1.SelectedItem;
    }

Also, using the Chart Editor at runtime means works as expected when changing the Gradient Direction. The Chart Editor at designtime seems to be the only area in which this issue occurs.
Comment 2 christopher ireland 2015-03-03 09:48:17 EST 
Last comment inaccurate, code snippet can reproduce issue with Utils.Caches = true.