version: v3, RELEASE 3.2.2746.19159
When using a TChart w/ a CircularGauge series, the GetAxisLabel and GetNextAxisLabel events are not raised.
Search found 5 matches
- Tue Jul 24, 2007 2:35 pm
- Forum: .NET
- Topic: TChart events for CircularGauge not raised
- Replies: 1
- Views: 4301
- Tue Jul 24, 2007 1:15 pm
- Forum: .NET
- Topic: CircularGauge.Axis.Labels.Visible not working
- Replies: 2
- Views: 4689
Hello, In the meantime you can workaround the issue like this: private Steema.TeeChart.Styles.CircularGauge gauge; private void InitializeChart() { tChart1.Series.Add(gauge = new Steema.TeeChart.Styles.CircularGauge()); Bitmap bmp = tChart1.Bitmap; gauge.Axis.Labels.Visible = false; } Thanks! The a...
- Mon Jul 23, 2007 10:50 pm
- Forum: .NET
- Topic: CircularGauge.Axis.Labels.Visible not working
- Replies: 2
- Views: 4689
CircularGauge.Axis.Labels.Visible not working
How can I hide axis labels for a CircularGauge? Using the editor appears to remove the label but as soon as the program executes the labels are still visible. Setting CircularGauge.Axis.Labels.Visible = false; in code doesn't work either. tChart1.Axes.Left.Labels.Visible = false; also doesn't work. ...
- Mon Jul 23, 2007 6:14 pm
- Forum: .NET
- Topic: Gauge axis labels
- Replies: 1
- Views: 3470
Gauge axis labels
version: v3 teechart.net I'd like to have a gauge with axis labels at 0, 25, 50, 75 and 100 (0 is minimum, 100 is maximum). How can I configure the gauge and chart to do this? I've tried reducing separation to 0 and 1. I've set the axis increment to 25. I've set LogarithmicBase=false. If the minimum...
- Wed Jul 18, 2007 1:14 pm
- Forum: .NET
- Topic: TeeChart v3.NET - Great Job!
- Replies: 1
- Views: 3579
TeeChart v3.NET - Great Job!
I just upgraded to v3 and it's a drop-in replacement! We get all the new features without having to rewrite our existing app.
Thank you so much to your developers who didn't make breaking changes to the API while adding wonderful new features. It even works with the .Net 1.1 framework!
Thank you so much to your developers who didn't make breaking changes to the API while adding wonderful new features. It even works with the .Net 1.1 framework!