Uwe Raabe

This question implies that it is shown on purpose. Most likely it is not.

Known issue: Invoking IDE Insight using Ctrl + . shows gray box over input field

Oh, I meant to have heard that they are trying to eliminate the dependence on DotNet 🤔

I guess, it is more likely taken from .NET: system.threading.monitor

In contrast to software a roadmap is always released when its ready.

Basically it is working! It is just that sometimes the Structure View context menu (or the actions behind it) seems not to be properly updated. After opening the context menu from the IDE Designer, the Structure View context menu is working again. Qualifies for a QP entry I think.

That would only work if you have the same packages installed as Carlos has.

<OT>Some say: MOIN is enough, MOIN MOIN is just chattering. (MOIN is' genug. MOIN MOIN is' schon Gesabbel)</OT>

Are you sure you are looking at the registry part of the user starting Delphi? You can also search the registry for the value shown in the error dialog. BTW, could it be that you installed MMX for All users instead of the recommended current one?

I can assure you they did! (BTW, most of the beta testing is done in Virtual Machines) Even I did and I have had no issues as described above nor do I have those now.

Just remove the corresponding entry from the registry in HKEY_CURRENT_USER\Software\Embarcadero\BDS\21.0\Experts.

Just curious: Why you would need that check in the first place?

In the moment I am able to track it down to Delphi 7, but I am pretty confident that it exists since Delphi 1.

You already can do that: {$IF Declared(TCustomAttribute)}

Perhaps I didn't explain it well enough. In case my code contains a check like: {$IF CompilerVersion < RAD_Chicago} {$IFEND} {$IF CompilerVersion < RAD_Sydney} {$IFEND} {$IF CompilerVersion < RAD_Rio} {$IFEND} that may perfectly compile with a future Delphi version named Chicago incorporating constants RAD_Chicago = 63; // no offence ... RAD_Sydney = 34; RAD_Rio = 33; ... but fails with any compiler available today. So I still need this one file with all these declarations and independent from the compiler. Where would be the benefit of Delphi providing a bunch of different versions of such a file where most of them are probably outdated and thus useless? Imagine we have each Delphi version in a separate VM, where almost all of these don't have the latest version of this file. Getting all this working will result in way more hassle than having this file maintained in one place, copying that into each project that makes use of it and keeping it up to date with each new Delphi version.