Hello. I'm using latest Steema.TeeChart.NET 4.2022.9.26 in a .NET 5 Windows Forms application on Windows 10 21H2 . Sometimes left axis title overlaps left axis labels: https://i.ibb.co/Gdwgmqk/image.png How to separate left axis labels from left axis title to get rid of this overlapping? I didn't fi...

Christopher wrote: ↑

Tue Sep 20, 2022 10:19 am

This issue has been resolved, thankfully without the need for a change in the sourcecode.

Technically it is working now, thank you.
But for me it is quite strange that the same operations require different client code depending on the application target platform.

do please let us know if it resolves this issue for you. With latest version print preview dialog now shows up but with default (English) language. I set language in my form constructor with: Steema.TeeChart.Languages.Russian.Activate(); but print preview dialog still looks like https://i.ibb.co/3f...

Christopher wrote: ↑

Mon Sep 19, 2022 7:39 am

We've been able to reproduce this issue here and have added it to our issue tracker with id=2551.

As I can see the issue was fixed within 1 hour - bravo! Looking forward to a nuget package update

Same code in .NET Framework 4.8 application (with very same Steema.TeeChart.NET version 4.2022.5.26) works as expected:

Hello. I'm using Steema.TeeChart.NET 4.2022.5.26 (that also reproduces with latest 4.2022.8.23 ) in a .NET 5 Windows Forms application on Windows 10 21H2 . I just added a chart on my form and added a line in it. My code is simple: public partial class Form1 : Form { public Form1() { InitializeCompon...

Thank you, BeforeDrawPoint event is working correctly. But but I'm still curious why GetPointerStyle event woks unexpected way?

Hello. I've tried to use GetPointerStyle event to apply different styles to line segments as described here : private void Form1_Load(object sender, EventArgs e) { var lineChart = new Line(); lineChart.LinePen.Width = 2; lineChart.Pointer.Style = PointerStyles.Circle; lineChart.Pointer.Visible = tru...

Thank you for your explanation, it is really useful to us. I now have a very clear idea of your situation, and will recommend to my colleagues that we do not pull the .NET 5.0 version out of our NuGet packages for the time being. Thank you, really hope they will hear you. BTW the same situation wil...

I had hoped Microsoft would support this last version of theirs for a few months before ending its life but no, you're right, it seems they prefer to release new binaries with no support at all. Yes that looks really strange.. I'm not sure if you're being serious here or not—is it true that your pr...

The latest public version is now v.4.2022.5.18 and will include the .NET 5.0 build until it reaches end of life. .NET 5.0 already reached EOL 8 days ago (10 May 2022) :D Decpite of that I hope you will not drop .NET 5.0 support in following builds - like many other developers I'm stuck on Visual St...

We'd like to encourage you download and test this version of TeeChart, and to please let us know any problems you have with it. I've peformed a simple test - TeeChart v 4.2022.4.26 works fine. Finally you've made it (just 2 weeks before .NET 5 EOL :D), many thanks. Latest TeeChart v 4.2022.5.16 cra...

it seems to me ridiculous that we should have to pack a NuGet into our Charting control to enable the Visual Studio designer to work as expected Yes this looks strange. I also agree that Microsoft has recently made the most disagreeable U-turns on its plans I'm afraid I don't quite understand what ...

Let's see if we get a response to this: https://github.com/dotnet/winforms/issues/4451 Hello again. I've recently created another issue on github regarding docs for WinForms Designer SDK (that are vital for finally implementing chart editor box on .NET 5). Some days ago I've tagged your github acco...

Using the code on the issue itself , I've just run it using .NET 6 SDK version 6.0.100-rc.2.21505.57 in Microsoft Visual Studio Enterprise 2022 Preview (64-bit) Version 17.0.0 Preview 5.0, using .NET 6 as the target Framework in the Core4451 project. Unfortunately the issue can still be reproduced ...