Uwe Raabe

I am already investigating that. Unfortunately I cannot reliably reproduce it here.

Indeed! After trying several other approaches I reverted my build machine back to 10.3.1 to provide a compatible version. Believe me, I am not amused - to say the least.

For an IDE package to work in Delphi 10.3, 10.3.1 and 10.3.2 it has to be compiled with 10.3 or 10.3.1 in the first place. The compatibility patch is needed to make such an application work with 10.3.2 (actually the patch is meant for 10.3.2 installations only). There is no way to make a package compiled with 10.3.2 work with 10.3 and 10.3.1. This case is a bad combination of first breaking compatibility by accident and then refuse to fix it because that would break some other compatibility.

Highlight the text with the mouse and click on the then appearing Quote bubble:

AFAIK, IndexDefs (as well as FieldDefs) are stored in the DFM when StoreDefs is True, but I guess they are not part of the data file.

OK, I found why I thought the problem to be fixed: It happens only under some complex conditions which were not always satisfied in my test configuration.

Indeed. Not sure what scenario I tested then. I am also wondering what Unit Dependency Analyzer has to do with it.

Seems like the docs are mistaken here. The source code is more reliable and shows that subkeys are internally deleted.

ArcTan2 produces the same result when both of its parameters are multiplied with the same factor. Thus dividing both by cnt before calling ArcTan2 has no influence on the result. In addition, ArcTan2 is pretty well capable of handling some special values like c = 0 (at least in non-ancient Delphi versions). There is no need to catch this case in advance.

This is a quote from Knuth's C adaptation of the original Adventure game by Will Crowther:

Unfortunately some companies insist on having their corporate styling being reflected in their applications. Just because some colors are different from the Windows standard doesn't mean that one needs to learn how to use that UI. That is more related to uncommon handling of TAB vw. ENTER keys or the misuse of well known shortcuts.

Looks like this issue: Bug In popupMenu with VCL Style - fixed in 10.3.2

As there seem to be people with different expectations, it would be best to make that configurable: Selecting Layout doesn't remember which monitor a form is on

At least that is much easier now than with these older Delphi versions.

While this may suit a single threaded application, the pooling approach is the recommended way for multi-threaded DB access. http://docwiki.embarcadero.com/RADStudio/Rio/en/Multithreading_(FireDAC)#Connection_Pooling

Known issue: No visual marks of modified files

That is not the usual behavior. There must be something special in your installation. Can you provide detailed steps?

Tools > Options > User Interface > Editor Options > Display > Number All Lines http://docwiki.embarcadero.com/RADStudio/Rio/en/Display

As I never had such an issue, I simply cannot tell. Perhaps creating a new dproj for each project affected helps.

It is not a general problem with the IDE. Otherwise I wouldn't be able to work efficiently any more. When there is nothing suspicious in the groupproj file, it might be something special in the dproj files.

Perhaps you are missing this line after the call to AddConnectionDef? FDManager.Active := true;

Are you aware of this function from IOTAServices? { ExpandRootMacro will change a string that contains $(BDS) or any $(name) and expands that environment variable. So for example $(BDS)\bin will be expanded to C:\Program Files\Embarcadero\10.0\bin assuming that BDS=C:\Program Files\Embarcadero\10.0 } function ExpandRootMacro(const S: string): string;

If you can provide reproducible test cases, you should send them to Peganza. They are always interested in cleaning out those glitches.

Well, that would require some sort of compilation or so and is definitely outside the scope of such a tool. It might be worth to investigate in interpreting the output of Peganza Pascal Analyzer Uses Report and act accordingly. This would eliminate the burden of analyzing the code.

Set Compressed=0 See above.