dummzeuch

That's not quite true. They will usually allow you to continue your subscription if it run out not too long ago. But of course starting with the date it run out. Also, there are some special offers from time to time, where you can save part of the price for a new license. But for a while keeping the subscription active has been the cheapest way to update (if you can call that "cheap"). And every time you have to remove "platinum support" from the order. The one thing that has annoyed me the most, is that you need an active subscription to even download an install bugfixes.

My experience is definitely different: Changing an include file does not force the units that include it to be recompiled.

Is there a way to call a 64 bit dll from 32 bit Delphi code? As far as I know that's not possible, but I have been wrong before. I am aware of this Article on Process Interoperability on Learn Microsoft.com. And there is Using 64-bit DLLs in 32-bit Processes with Out-of-process COM which is about C# and WoW64Injection: Loading a 64-bit DLL in a 32-bit process which probably won't help at all. (Hm, maybe this should have gone to RTL + VCL ?)

Move the code to an empty unit and try to compile that one. If it still does not compile post the full code of that new unit here. I think the problem is not in the code you have shown us but somewhere before that.

No, simply two monitors with different resolutions (and different scaling): Just to make this more difficult, monitor 2 (1920x1200 scaled 100%) is the main monitor, so all positions on monitor 1 (3840x2160 scaled 125%) are negative x (-1 to -3839) and some are even negative y. I always put the IDE on the right 2/3 of monitor 1, that's why saving and restoring desktops in Delphi IDE's is broken on my setup since Delphi 11. Also this is the reason that scaling in the Delphi IDE is broken on my system (and my home grown scaling in GExperts is very difficult to do and still has some glitches).

AI will feature prominently in the release announcement, that's for sure, but from what we have seen in Marco Cantu's blog posts so far there is definitely more.

Yes, definitely. Negative positions are totally normal, if a form is on a monitor left or above the main monitor. And the code is definitely broken, because it uses "with screen do". Using screen isn't necessarily wrong though as it should include all monitors, but it assumes that the visible area is a rectangle, which may not be the case (it isn't in my setup).

According to https://www.advdelphisys.com/help/ads_keys_u.html Ctrl+O+C starts column selection mode or with the mouse Click+Alt+mousemove (https://docwiki.embarcadero.com/RADStudio/Sydney/en/Default_Keyboard_Shortcuts)

I wonder whether there will be a code formatter that supports this. Given that they deprecated the existing one since Delphi 11, I somehow doubt it.

There is always the return address on the stack. Which you can get by calling ReturnAddress But I guess you don't want an address but a function / method name? JclDebug offers some functions for that: https://stackoverflow.com/questions/1301254/how-to-get-current-methods-name-in-delphi-7 Or as described here:

Excactly, why don't you? These people know about this detail? I would have expected that they had never seen any Pascal code and even if they did, that they wouldn't have noticed the way variable declarations work there.

If I remember correctly there is no way to access the compiler messages through the NTA because the output goes to a modified VirtualStringTree (but if you find one I would be very interested indeed). But the OTA might give you that access, I haven't checked.

If the NTA offers advantages to your plugin you can always add that later. Whether that's the case depends on what your plugin does.

I hereby apologize to Embarcadero. They replied on the same day to our general purchasing account (which was correct because that is the email address used to register the licenses). Somehow I must have missed that reply several times when I looked there. And I managed to fix the problem too, even though I am still not sure what I did wrong the first time. And thanks to Devid Espenschied for clearing that up.

Thanks for the reminder. I had totally forgotten about Devid and have now contacted him directly. (You might want to remove his email address from your post to prevent spam.)