Hello Florian, I hope you find this more helpful: Private Sub InitializeChart() Dim line = New Line(tChart1.Chart) line.FillSampleValues() End Sub Private _flag As Boolean = False Private _custom As Axis = Nothing Private Sub SetCustom() _flag = Not _flag If _flag Then tChart1(0).CustomVertAxis = _c...

Hello Florian, You will need to specify a value for the LeftMargin of the Panel class to shift the Custom Axis across, e.g. private void InitializeChart() { var line = new Line(tChart1.Chart); line.FillSampleValues(); } bool _flag = false; Axis _custom = null; void SetCustom() { _flag = !_flag; if (...

Hello - The following code running with TeeChart.WPF.dll v.4.2019.5.15 works as expected here: private void TChart1_MouseDoubleClick(object sender, MouseButtonEventArgs e) { var ms = new MemoryStream(); tChart1.Export.Template.Save(ms); ms.Position = 0; tChart2.Import.Template.Load(ms); } Could you ...

bairog wrote: ↑

Fri Jun 07, 2019 11:23 am

Thank you for your job.

You're very welcome. Just to let you know that we've added six new NuGet packages here:
https://www.nuget.org/profiles/steema

These are TeeChart for .NET Core 3.0 Pro/Business for .Net Core 3.0, .Net Core 3.0 Windows Forms and .Net Core 3.0 WPF.

Hello! We will be in touch with you personally as soon as we have a version of TeeChart.NET for .NET Core 3.0 which we feel is ready for client testing. We've created a test NuGet package for .NET Core 3.0 preview 5 Windows Forms which you can download from here . You will be able to install this Nu...

Hello,

please find attached a Visual Studio project which correctly replicates the code I gave you in my last post:
Can you please modify the code in this project and post it back here so I can reproduce your problem on my machine?

Hello, Can you guess what the problem is? Do you have the Back Wall set to visible? Using the following code works as expected here: public Form1() { InitializeComponent(); InitializeChart(); } private void InitializeChart() { tChart1.Series.Add(typeof(Line)).FillSampleValues(); tChart1.Walls.Back.V...

Any progress for now? Is there a new version to test? Not at the moment, no. As far as we understand from this blog post here , the roadmap for .NET Core/.NET looks like this: dotnet_schedule.png We here at Steema Software are committed to complying with this timeline, and will have versions of Tee...

I guess my question is there any way to get grid lines to be drawn at the start and finish of each axis, and if not, is there any other way of accomplishing the effect I am after? Well, you could try adding the following two lines to FreqAxisAdditions() and VoltAxisAdditions(): objAxis.MinimumOffse...

BIQ wrote: ↑

Thu May 02, 2019 6:14 am

Please let me know if i can provide any additional information.

Yes please - would you be so kind as to give us some code with which we can reproduce this issue here?

But given what you already have it should be trivial for you to make it do what I want :wink: :!: :!: :!: Of course! :D But seriously, if you'd like us to give you a quote for the work, do please write to sales@steema.com and we'd be happy to give you one. It is not trivial getting GDI+ to behave l...

Hello,

have you found the Rotate tool? There's an example of it in the Feature Demo you can download from GitHub here:

Hello Rob, some code: public Form1() { InitializeComponent(); InitializeChart(); } Line _line = new Line(), _line1 = new Line(); private void InitializeChart() { tChart1.Series.Add(_line); tChart1.Series.Add(_line1); _line.FillSampleValues(); _line1.FillSampleValues(); } private void button2_Click(o...

Hello, We are preparing the existing TeeChart version for tests in the Net Core 3 Framework. We expect to be able to make a test version available soon. In the meantime, the current TeeChart NetStandard version can be used as a non-forms control - please find following an example of the use of TeeCh...

Hello,

thank you, I can confirm this as a bug and have added it to our issue-tracking software with id=2187 - as you can see, this issue has been marked as completed, which means a fix will become available in a new NuGet package very shortly.