Lajos Juhász

Just now, Shrinavat said:

My favorite IDE is finally catching up to the current decade? Color me mildly intrigued. It's a 64-bit IDE, the worst-kept secret since someone figured out Clark Kent was Superman.

I doubt that 64 bit version of the IDE is going to be available in a minor release. We can only hope. IBM is also catching up and deprecates the 32 bit drivers for Informix, I do need a 64 bit IDE. 

(The source code for application is prepared to be compiled as a 64 bit due to poor debugging we did not made the change yet. On the other hand I am a bit afraid as users are going to load 3-4GB data from the database)

It is not (yet) addressed in Delphi 12.2 it still defaults to 0 instead of 1.

2 hours ago, c0d3r said:

NO output in the memo field after exit from Modern StandBy mode.

In my case the timer continues to fire after sleep.

The following sleep states are available on this system:
    Standby (S0 Low Power Idle) Network Connected
    Hibernate
    Fast Startup

At procedure TIdCustomTCPServer.Shutdown before the threads are terminated StopListening is called:

//APR-011207: for safe-close Ex: SQL Server ShutDown 1) stop listen 2) wait until all clients go out
 

5 minutes ago, narag said:

I'm using a TIdHTTPServer component and I would like to know, after its Active property is set to False, when all the current threads have finished serving. 

It should be done as the SetActive returns. If You look at the source code SetActive will call Shutdown that will call TerminateAllThreads.

12 minutes ago, ventiseis said:

Perhaps its time for a 64bit IDE. 

Or make fewer circular references. Moving everything in the code to interface section is wrong. It is well known fact that the uses are only for those units that are required in the interface section, everything else must go into the implementation section. Other crucial thing is to remove the Unit Scope names and in code use only fully qualified unit names. This was important in older versions of Delphi (there were problems with unit name caching). 

FMX or VCL does not matter as Json implementation does not depend on the visual library.

It does not in my case using Task manager.

Before the string is read the working set is 3,752K. Read the string: 4,652K, parsing the json 7,280K, freeandnil - 4676K, when the click method is finished the memory set is back at 3,660K.

I cannot reproduce the leak using Delphi 12.2

Delphi in order to survive must ASAP include the method to close a modalForm or we will die. As a Quick Fix they should include the class helper for all the existing versions:

type
  TFormHelper = class helper for TCustomForm
  public
    procedure EndDialog(PModulResult: TModalResult);
  end;

{ TFormHelper }

procedure TFormHelper.EndDialog(PModulResult: TModalResult);
begin
  modalResult:=PModulResult;
end;
 

I can only hope that somebody from Embarcadero will read this thread and will push these changes directly to the TForm not to require a class helper for such an important issue to be fixed.

(For years I was using the modalResult to close modal forms without a single issue. This thread made me realize that Delphi is dying because it does not have such a method.)

1 hour ago, Der schöne Günther said:

I haven't really kept up with the latest Delphi versions. Is still still the same problem with the LSP from 2020, or is this something else?

Recently I have a different problem when debugging using Delphi, Windows freeze completely. Even the task manager cannot be activated, the only solution is to turn off the laptop using the power button. 

2 hours ago, Anders Melander said:

Yes, yes, we see now. How could we have been so blind? Totally different things. Totally!

Instead of running away from this terrible problem. Anders you should write a class helper to help to solve this gigantic bug in the design. I mean how can we live and use Delphi knowing that it has this very poorly design in the fundamental part of the VCL.

You should write:

 

procedure TTestForm.DBGrid1DblClick(Sender: TObject);
begin
  ModalResult := mrOK;
end;

There is no need to call Close at all. You can thank later to Delphi for implementing correctly.

Does it change if you change the CharCase from ecUpperCase to ecNormal?

1 hour ago, marcovaldo said:

I am somehow afraid that the issues might not be technical or business but maybee political (sanctions etc.) of nature.

https://blogs.embarcadero.com/eugene-kryukov-father-of-firemonkey-and-incredibly-talented-developer/?utm_source=facebook&utm_medium=social&utm_content=fatherOfFiremonkey

Reading the code I believe it is the:

procedure TMyCustomCalendar.CreateWnd;
begin
  inherited CreateWnd;
  RecreateWnd; // Force the control to redraw and send MCN_GETDAYSTATE
end;
 

Why do you want to create windows handle all the time? (just after it was created?)

16 minutes ago, bravesofts said:

How can I implement a Delphi variadic method that allows calling it without brackets, similar to Write/Writeln?

This has been done using compiler magic. You can not create such a function.

On 1/4/2025 at 11:28 AM, GabrielMoraru said:

I used FMX some years ago and I don't remember having any of this problems. Is FMX getting worse instead of better?
(Rhetoric question)

Since mobile platforms are changing so fast. It really depends at what moment you compare. At anytime the state of Delphi can be better or worse than last time. In 2100 when the mobile platforms are going to be stable like desktop you can expect a better integration with Delphi.

On 1/4/2025 at 11:28 AM, GabrielMoraru said:

I used FMX some years ago and I don't remember having any of this problems. Is FMX getting worse instead of better?
(Rhetoric question)

Since mobile platforms are changing so fast. It really depends at what moment you compare. At anytime the state of Delphi can be better or worse than last time. In 2100 when the mobile platforms are going to be stable like desktop you can expect a better integration with Delphi.

On 1/4/2025 at 11:28 AM, GabrielMoraru said:

I used FMX some years ago and I don't remember having any of this problems. Is FMX getting worse instead of better?
(Rhetoric question)

Since mobile platforms are changing so fast. It really depends at what moment you compare. At anytime the state of Delphi can be better or worse than last time. In 2100 when the mobile platforms are going to be stable like desktop you can expect a better integration with Delphi.

It was a couple a decade ago when I wrote my previous C code. At that moment x is out of scope You should use sum to hold the result:

sum +=myArray[x]

cout << "The sum is: " << sum << endl; 

I believe the 3rd character in the 10th line of your code is wrong. On a more serious note without any details what the server expects and how you tried to connect we can not help.

You wrote the best solution onChange. With this you might covered some situation. What for the case when instead of key down the user click on the row below or above?

You will have to debug the code. I've tested on a couple of reports it is working for me.

1 hour ago, Rollo62 said:

I wonder why Embarcadero is not offering an easy and stably native payment solution, or at least a valid tutorial howto get there.

Mobile platforms are changing very fast. Sometimes it is difficult for Embarcadero to provde a solution in a reasonable time frame when the new requirements are released to be able to continue to compile for new versions. Unfortunately nowdays Delphi support too many platforms. They are playing catch up games against other products. Delphi is by rule almost always way behind.