ST 2.1 RC2 - Line chart fill cannot be disabled

[heath.hansell]

When creating a chart with a line series that has a colors definition and fill: false, the fill is still set.

e.g.

    getNewSeries: function (colors, fields, index, field) {        var t = Ext.Array.filter(fields, function (f) { return f.name === field; })[0].header;
        return {
            type: 'line',
            title: t,
            xField: 'c0',
            yField: field,
            style: {
                stroke: colors[index],
                miterLimit: 3,
                lineCap: 'miter',
                lineWidth: 2
            },
            smooth: true,
            fill: false,
            showInLegend: true,
            marker: {
                type: 'circle',
                radius: 4,
                fill: colors[index]
            }
        };
    }

Ext.chart.series.Series - commenting out the line below in an override and it works again.

   
updateColors: function (colorSet) {
        // this.setSubStyle({fillStyle: colorSet});
        this.doUpdateStyles();
    }

[mitchellsimoens]

According to the docs fill is not a config of the line series. Using the kitchensink the fill is within the style config object.

[heath.hansell]

Looking at the docs, clicking code editor on Ext.chart.series.Line, the second line has fill:true

Also underneath it states:

The second series has fill = true which means that the line will also have an area below it of the same color.

[mitchellsimoens]

If you are looking at http://docs.sencha.com/touch-charts/1-0/#!/api then you are looking at the wrong product. Touch Charts are not a valid product, charts are now build within the framework in 2.1.0 so if you look at docs that come in the 2.1.0 releases you will see that the Line series does not have a fill config.

[heath.hansell]

Here's a screenshot of the documentation I have from the 2.1rc2 release
Ext.chart.series.Line - Sencha Docs - Touch 2.jpg

[mitchellsimoens]

Screen Shot 2012-10-16 at 8.34.18 AM.png

But look at the configs. This is a doc issue

[greg.barry]

Thanks for the report! I have opened a bug in our bug tracker.