Uwe Raabe

So your certificate has been issued in 2022 and thus doesn't fall under the new hardware rules. You can use it as long as it is valid, but then you need one of the new ones bound to a hardware token.

That won't catch the keys pressed inside the grid itself. The BeforeInsert event is indeed the best place.

I would rather say that are 21 seconds (which is probably less than I actually need to just read the description). This is backed by this quote from the About text: Since the start time of each puzzle is way out of my awake periods a day, I can thankfully ignore the ranking system completely. This allows me to concentrate on finding a suitable solution, sometimes even a clever one.

Is this folder is added to the PATH variable or how do you make Windows find those libraries? Also, which folder is given as the starting folder when you launch the application?

A TEdit can only show one line. For multi-lines use a TMemo instead.

I try to omit the control type in the name in favor of the purpose the control is used for. F.i. instead naming a TLabel as lblSomething and a TStaticText as sttSomethingElse I use dspSomething, dispSomething or even displaySomething lately. Similar I give a TEdit, TMemo or TComboBox (if not in List style) a editSomething name, while a TRadioGroup, TLIstBox or TComboBox (when in List style) gets a name like selectSomething. The advantages are that these names usually stay as is when the controls are changing type and it contributes to documentation - at least a little bit.

A bit tedious, but you can set a breakpoint by pressing F5 in each line from 2 to 7 and use F9 instead of F8. (Not that I would rate that a good solution, but my perception may be different than yours.)

With inline vars this works: Var Boy, Girl, Couple: string; But this does not: Var Boy: string; Girl: string; Couple: string;

You are using inline variables. Try moving the variables declaration before the begin. procedure TFormStringConcatenation.ButtonAddCoupleClick(Sender: TObject); Var Boy: string; Girl: string; Couple: string; begin Boy := EditEnterBoy.Text; Girl := EditEnterGirl.Text; Couple := Boy + ' and ' + Girl; ListBoxCouple.Items.Add(Couple);

Could it be VAT?

Well, MMX was born in 2001 and I assume the help is just as old.

Sending is done via MAPI, so no special handling for some mailers. You can check or set the MAPI entry under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Messaging Subsystem/ and /HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows Messaging Subsystem/ for a REG_SZ value of 1. The help gives some information:

Have you tried using ToString instead of ToJSON?

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.