Uwe Raabe

When you sell to larger companies? Definitely! Most likely they will never make it to be your customers.

The TRecordA/TRecordB relation leads to a structure of infinite size. I would question the design choice, but having no knowledge of the underlying API that is not more than just a gut feeling. IMHO, you should use the approach that fits best. There is no general rule for all cases.

The RSP issues are from the Old Quality Portal (now read-only). Although they are not visible in the New Quality Portal, they still exist in the internal tracking system.

There was a change in V15.1.10 that prohibits the Auto-Scan until the search window is visible. I had a couple of reports about errors regarding hidden windows in this area. Seems I have to think about a more sophisticated fix for that. Perhaps prohibiting the display instead of the search would be more suitable.

While TApplication checks IsShortCut for the main form only, each form also checks IsShortCut for all its child components (direct and indirect). Your options to get the TActionList on the datamodule executed is either make the datamodule owned by the mainform or wire the OnShortCut event handler of TApplication and call the actionlist IsShortCut manually.

Could it be related to this one: RSP-18189 - Duplicate items in component palette

With WordWrap = True, the AutoSize property of a Vcl TLabel doesn't work the same as without. BTW, almost the same holds true for FMX.

Not sure what happened in your case, but for me it was just executing the setup, confirm any questions and re-compile one package to get it working again.

May depend on the current filter and search criteria you use: https://embt.atlassian.net/servicedesk/customer/portal/1/RSS-1944

Despite its name the TTARRAY declaration is a set and not an array, but sets are limited to elements with ordinal 0..255.

I'm working with 12.2 Patch 1 on my productive system now for five days and I also don't see any problems debugging. The only problem appeared directly after the update, caused by an internal package compiled without the patch and resolved by recompiling. The build system was updated before to allow for testing the compatibility of packages compiled with Patch 1 on a system without.

Probably because at that time pointers were still 32 bit only.

And Embarcadero still refuses to implement this feature request (despite its 188 votes): RSP-35301 - Option to design in Screen PPI but save in 96 PPI For me and quite a couple of other users that is mandatory for using the IDE in High-DPI.

@PeterBelow It is even possible to inject new properties to the Object Inspector. In Cmon.DataSense.Design.pas I use this technique to add a DataSource and DataField property to supported controls. The additional data is stored in a special component (TDataSense) using a dictionary internally:

That sounds more like Quantum Mechanics than Mathematics.