Uwe Raabe

I can confirm that KB5020435 solves this issue on my system. As Windows Update didn't list it, I had to download and install it manually

I don't know if all is necessary, but I at least it is sufficient: have a field for the sub component exposed as a published read-property create the instance in the constructor (Self as Owner is allowed omitting the Free in the destructor) call SetSubComponent(True) after creation set all properties as needed don't forget to set Parent

There simply is no license for older Community Editions than the current one. CE licenses are restricted to one year. After that one can get a new license but for the then current version only. If you need to use an older Delphi version you are supposed to buy a full Delphi version, where the license covers older versions, too.

I guess, that is not one of the use cases the developers had in mind when they designed the custom component system. AFAIK, you can either have subcomponents created dynamically with their properties stored as sub-properties of the outer component or you can have a frame stored in the object repository with derived instances in your project.

Can you show the code for the custom component?

Yes, the problem is Windows 10 only.

I managed to get it working with the following steps: In the registry add a subkey to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols named "TLS 1.3" Add another subkey to this new key named "Client" Add a DWORD to the Client key named "Enabled" with Value = 1 Add another DWORD to the Client key named "DisabledByDefault" with Value = 0 In the TRESTClient component of your example enable TLS13 in SecureProtocols Edit: You need to restart Windows to make the registry settings active.

Currently removing the Windows Update seems the only solution.

That one is new with 11.2 and it is indeed enabled by it.

$(SanitizedProjectName) gives the name of the project without extension.

What does that garbage look like?

Every task is different. Describe your task in detail and one can give some hints how to use these components for this task. You don't need a separate set of components for each part. The same components can be used in sequence with changed properties.

You can get the complete URL from TRESTRequest.GetFullRequestURL and the payload from TRESTRequest.Params.ParameterByName('body').Value (check for a nil parameter in case there is no body at all)

There also is a built-in function to decode HTML text: uses System.NetEncoding; ... var S := TNetEncoding.HTML.Decode(sHtml);

Application.MainForm is set with the first TForm created with Application.CreateForm.

Sorry, but I don't understand your question.

None that I am aware of. So far a I was under the impression to be able to find the cause in my own code.

Are you sure that the dataset is open?

Actually that is exactly the way to do it. It just seems that setting the Checked property of TDBCheckBox is not propagated to the underlying field. I need to investigate that and file a bug report as soon as time allows. As a workaround don't set the Checked property but the field value directly: chk.Field.AsBoolean := chk = Sender;

@haentschman Not all of the lower numbers still exist...

Oh, now I understand what you want to achieve. One solution would be to wire this event handler to each TDBCheckBox inside the TGroupBox: var DisableEvent: Boolean = False; procedure TForm747.DBCheckBoxClick(Sender: TObject); begin if DisableEvent then Exit; DisableEvent := True; try var grp := (Sender as TControl).Parent as TGroupBox; for var I := 0 to grp.ControlCount - 1 do if grp.Controls[I] is TDBCheckBox then begin var chk := TDBCheckBox(grp.Controls[I]); chk.Checked := chk = Sender; end; finally DisableEvent := False; end; end;

I cannot reproduce that. If I have several TDBCheckBox inside a TGroupBox each can be switched independently.

The patch does not enable that, but IIRC it is standard behavior since 11.2.

Can you please give an example?

You need more patience: