Die Holländer

Isn't the headerfile for C#?

I would appreciate it if the Indy discussions, along with other third-party components, could remain here on this forum. Since installing these components, I’ve primarily been using them, but I still enjoy following the discussions. If these conversations shift to other platforms like GitHub, I propably would not bookmark them all and visit them.

Is it possible to use the Afterdraw event to force the axis to be visible? procedure TForm1.Chart1AfterDraw(Sender: TObject); begin if not Chart1.Axes.Left.Visible then Chart1.Axes.Left.Visible := True; if not Chart1.Axes.Right.Visible then Chart1.Axes.Right.Visible := True; end;

I think nobody dares to talk about ChatGPT here on this forum anymore.

Silent paws tiptoe, Whiskers twitch in moonlit night— Graceful feline dance.

I view console applications not just as user (prompt) programs, but also as tools for performing tasks that just don’t require a GUI. We have numerous console applications that are often started by a task scheduler or installed as services. These programs are hard to write with scripts alone, which is why we use Delphi and its tools and libraries. (such as FireDac, sFTP and the mORMot HTTPs web server). These applications handle all the automated processes and tasks essential for our company. All the code can of course used in other projects for GUI or console applications.

In Delphi you just declare the unit where the functions you need are declared. For example Remy mentioned BoolToStr https://docwiki.embarcadero.com/Libraries/en/System.SysUtils.BoolToStr So, this function is in the System.SysUtils unit. In Delphi you can access that unit by declare it on top of your code: Uses System.SysUtils Now you can use the BoolToStr function in your code.

Console programming is easy with Delphi. The books will learn you the Delphi (Pascal) syntax and that is one of the most easy to learn of all the programming languages. That was dummzeuch's conclusion already 10 years ago: twm's blog Important : Console with parameters (With a Gui example..)

Its weird, but maybe it is something that is declared into the source of the Chart component. In my projects i managed over the years to get all the 3th party components without source out of the applications, apart from some of the native Windows. I would try to separate the form(s) with the Chart component from the application and continue the conversion of the application to the newer Delphi version. You can always try to compile the chart form as a separate application and create a communication with your main program to display the charts, like using the Windows Message system or creating a DLL.

Can you look into the TDBChart Unit code? I see in my version D12.2 that it is not installed as a default component..

For me its not a big problem. I already working a few months with it and I don't have to change the width of these panels. I noticed that in the debug layout it is working ok but it has also a minimum width.

The only way is to close it by that little pin. Then when you press on the closed inspector tab it slide open and you are able to make it smaller. But i find it nicer to have it open all the time..

Resize inspector.mp4

In my case when i make it large, like half way the screen, then I can make it only serveral times a tiny smaller, untill it reaches that strange minimum width..

I've the same behaviour. (D12 update 2) Also the Palette and Project ones does this. They are on both sides of the screen with the Palette under the inspector. (They use the same splitter) Lucky I saved my IDE desktop with the proper widths, so I can get them back to my default widths. I don't know why, but that doesn't make you dumb..