Lajos Juhász

No that's the limitation of the Delphi. It doesn't support exceptions during initialization of the application. The same problem has Skia if the dll is missing (of course in case of skia there is an easy fix replace the exception with showmessage).

You should open a bug ticket at Embarcadero Quality portal - https://quality.embarcadero.com/

18 minutes ago, FabDev said:

Open a big project with a lot of files (units, forms, dfm etc..). Select a word and do a search (CTRL + SHIFT + F).

I cannot reproduce, you must use some memory hungry components.

4 minutes ago, Alexander Sviridenkov said:

.dpr or .dpk?

dpk of course.

Great work, you should also consider to support packages (dpr files). 

15 hours ago, Sherlock said:

Yeah, Embarcadero sometimes fights with their servers. They'll come around eventually. I guess Delphi 12 is lurking, and the servers are being prepped for it.

You can only hope. I watched the C++ webinar to get an idea what we can expect from D12. The C++ part was far from finished.

17 minutes ago, Anders Melander said:

I think the IDE form designer might work around that; Only one design form can be visible at a time.

Just a guess.

It's not the case using Delphi 11.2. Tried to open some forms and the used GDI handles (according to the task manager) keeps growing and doesn't goes back.

1 hour ago, FabDev said:

And what happens when more than 100 forms are opened at the same time

In that case windows will run out of GDI handles and give error. A 64 bit version of the IDE would have the same problem.

You should try again, I can access it:

 

22 minutes ago, Rollo62 said:

My point is, if Embarcadero puts a lot of effort into multi-strings, then I'm asking what main purpose this should solve ?

That's easy. The only reason is that they can say that finally managed to copy it from other languages. Lately that's the only driving force behind the R&D.

https://docwiki.embarcadero.com/Libraries/Sydney/en/System.SysUtils.StrToCurr

Thousand separators and currency symbols are not allowed in the string. If the string doesn't contain a valid value, StrToCurr raises an EConvertError exception.

I would really like to see a list of problems that a 64 bit IDE could solve.

In the new Delphi roadmap there is a research area to replace the IDE code editor maybe that will bring us closer to 64 bit IDE.

In my opinion a 64 bit IDE would not solve the problems. I am from time to time working on a larger code base without a problem. A badly written pacakge can of course destroy the IDE.

1 minute ago, Attila Kovacs said:

Will this throw an error then?

I bet the beta testers cannot answer this question without violating the NDA. Earlier it was not allowed even to write about a fact that somebody is a beta tester.

In my opinion it would be better to use:

blub:= "line1
   line2, indented
line3
;

3 hours ago, FPiette said:

If you app consume memory but has no leak, then you have fragmentation.

Could be also objects with owners that are left in the memory. Those objects wouls use memory and be freed before the memory leak report is generated.

You can try https://github.com/Spelt/ZXing.Delphi. I did only a test for VCL and QR codes.

change your regional settings in the IDE. Set your keyboard to for example ENG US.

You cannot make the form in the IDE larger than the resolution of your screen you're working on. This is an insane limitation of the new IDE (can you bite if you have a 4k office monitor and have to work later on a laptop).

You should define your view in Tools -  Options. You can find it if you navigate to User Interface - Form Designer - Device Manager or just write Device manager into the search edit box at the top. 

https://docwiki.embarcadero.com/RADStudio/Alexandria/en/Adding_a_Device_Preset

My only experience with this kind of debugging is that it's going to result a request time out.

46 minutes ago, FPiette said:

Is Delphi-Praxis written in Delphi or PHP or something else ? Is it a standard product or whatever ?

Hint: Powered by Invision Community.

I cannot fully understand the question either. My bet is that the TDBgrid for blob fields instead of the value displays (Memo). In order to correct that a solution is to use  the OnGetText event of the TMemoField/TWideMemoField:

Quote

procedure TForm3.FDQuery1MyMemoFieldGetText(Sender: TField; var Text: string; DisplayText: Boolean);
begin
  if DisplayText then
    Text:=Sender.AsString;
end;
 

3 minutes ago, Uwe Raabe said:

Relying on unit scope names also makes the compiling slower.

For me it made unstable. There was no chance to do compile all for a large project group. The solution was to add scopes to unit names and improve code structure and reduce circular references.

For me MMX Code Explorer works perfectly to reduce circular references (Unit dependency Analyzer). For compiler stability possible it's more important to write the entire unit name eg. Winapi.Windows instead of Windows and having a large list of unit scopes names in the options.