Uwe Raabe

Indeed. I also add am IFDEF to error out when compiled with a newer Delphi version. Even if the problem is not fixed yet, the tweaked source is most likely no longer up to date anymore.

Can you show some actual and complete JSON content?

A fresh VCL forms application shows a Delphi icon in front of the window title. What did you do to remove that?

Yes, it is called Build Groups: Do you know Build Groups?

There are several people complaining about too many new things added to Delphi in the last years instead of old bugs being fixed. Now I am confused...

It is as well possible that it shows up here just because it is installed.

Well, here it is:

IIRC, Andy has been offered a free license at least twice, but he reclined.

It is not! A cast tells the compiler to treat the given memory address as if it were of the casted type. To get a supported interface out of a class instance one has to call QueryInterface, which in the end is what the AS operator does.

Good suggestion! I will note a feature request for it.

That is a common scenario and usually works well. In my case I have about a dozen 3rd party libs shared between different projects, where each references a certain revision. When I decide to update that project to a newer version (not necessarily the latest) this can be done with minimal effort. Repos with inhouse shared code are treated the same way as if they were 3rd party ones.

In case you don't need the name you can also assign it to an empty string. Unnamed components can coexist inside their owner.

Well, I don't have a practical example at hand in the moment and some academic ones would be of no value. Nonetheless, I will try to think of some, but as always there will be other ways to achieve the same goal - whatever that will be.

A quick check didn't show that behavior, but the missing information is: It happens only when there already are build groups defined in the project group. For a new project group you can create and edit build groups until you close and re-open the project group. Once the error appears it will persist even with new project groups until the IDE is started again. Would you please file a report in QP for that?

Can you show a screenshot?

When a TComponent is inserted into another TComponent (like a TButton into a TForm) it tries to connect that component to a published field matching the name of the component. The responsible code part is the SetReference call in TComponent.InsertComponent. That is one reason why the Form Designer adds the component fields as published. Side note: You can even take advantage of this mechanism for your own needs. It is not restricted to the streaming system.

No, it is the name of the variable that contains the object. The name of a TComponent instance can be different from the names of the variables containing that instance.

I am unsure what you expect, but in this code procedure TConcrete.Method(aObjectEvent: TNotifyEvent); begin aObjectEvent(Self) end; the parameter Self represents the instance of TConcrete. As long as you don't give a name to that instance like in this code sequence fBASE := TConcrete.Create(nil); try fBASE.Name := 'My Name'; // give fBASE a name fBASE.Method(Btn_Normal_Event.OnClick); finally fBASE.Free; end; the Name property remains empty. But as I already mentioned in the beginning: It is quite unclear what you expect.

I would like to add some candy to the code above. If you add three published fields to the form which names and types matches the ones in the clipboard text (which are predictable when created with the Rest Debugger), you can access the imported components by these fields: type TForm649 = class(TForm) Button1: TButton; Memo1: TMemo; procedure Button1Click(Sender: TObject); private public published RESTClient1: TRESTClient; RESTRequest1: TRESTRequest; RESTResponse1: TRESTResponse; end; procedure TForm649.Button1Click(Sender: TObject); var binary: TMemoryStream; cmp: TComponent; lst: TStringList; stream: TMemoryStream; begin { clear any existing instances } FreeAndNil(RESTClient1); FreeAndNil(RESTRequest1); FreeAndNil(RESTResponse1); lst := TStringList.Create; try lst.Add('object myName: TComponent'); // this resembles the instance given as parameter to ReadComponent lst.AddStrings(cArr); lst.Add('end'); stream := TMemoryStream.Create; try lst.SaveToStream(stream); stream.Position := 0; binary := TMemoryStream.Create; try ObjectTextToBinary(stream, binary); binary.Position := 0; binary.ReadComponent(Self); // Self puts the code into the form itself, but any other component will do finally binary.Free; end; finally stream.Free; end; finally lst.Free; end; Memo1.Lines.Add(RESTRequest1.Params[1].Value); end; You can even omit the RegisterClasses call then. The FreeAndNil of the three fields guarantees fresh components being created. It is as well possible to keep existing instances, but that can end up having properties with non default values when these are not included in the stream. (That may even be desired in some cases.)

At least it is documented here: https://docwiki.embarcadero.com/RADStudio/Alexandria/en/Structured_Types_(Delphi)#Dynamic_Arrays

I have hacked together some code that may help here. Create a new VCL Forms Application, drop a button and a memo onto the form and use the following code: const cArr: TArray<string> = [ // 'object RESTClient1: TRESTClient', // ' BaseURL = ', // ' ''https://api-eu1.XXXXXXXXXXXXXXX/ORD''', // ' Params = <>', // 'end', // 'object RESTRequest1: TRESTRequest', // ' AssignedValues = [rvConnectTimeout, rvReadTimeout]', // ' Client = RESTClient1', // ' Method = rmPOST', // ' Params = <', // ' item', // ' Kind = pkHTTPHEADER', // ' Name = ''x-api-compleat-key''', // ' Value = ''0aXXXXXXXXXXXXXXXXXXXXXX94''', // ' end', // ' item', // ' Kind = pkREQUESTBODY', // ' Name = ''body9BE6CF603159471FB026D7FF6FC3D2DB''', // ' Value = ', // ' ''{"master_id":1,"LayoutID":"d967cc4c-5b2b-4474-8cac-a71f9684ee70"'' +', // ' '',"TransactionStatus":"SAV","Reference":1,"PoNumber":"ORD1","Date'' +', // ' ''Created":"2008-07-08","SupplierName":"TMB","CurrencyCode":"GBP",'' +', // ' ''"SupplierID":"1234","LineItems":[{"master_id":1,"Description":"G'' +', // ' ''obo Original","UnitCost":"100.00","Net":"100.00","Quantity":1,"T'' +', // ' ''ax":0,"Gross":100},{"master_id":1,"Description":"Gobo Copy","Uni'' +', // ' ''tCost":"50.00","Net":"100.00","Quantity":2,"Tax":0,"Gross":100}]'' +', // ' ''}''', // ' ContentType = ctAPPLICATION_JSON', // ' end>', // ' Response = RESTResponse1', // 'end', // 'object RESTResponse1: TRESTResponse', // 'end', // '']; procedure TForm649.Button1Click(Sender: TObject); var binary: TMemoryStream; cmp: TComponent; lst: TStringList; stream: TMemoryStream; begin RegisterClasses([TRESTClient, TRESTRequest, TRESTResponse]); lst := TStringList.Create; try lst.Add('object myName: TComponent'); // name doesn't really matter lst.AddStrings(cArr); lst.Add('end'); stream := TMemoryStream.Create; try lst.SaveToStream(stream); stream.Position := 0; binary := TMemoryStream.Create; try ObjectTextToBinary(stream, binary); binary.Position := 0; binary.ReadComponent(Self); // Self puts the code into the form itself, but any other component will do finally binary.Free; end; finally stream.Free; end; finally lst.Free; end; cmp := FindComponent('RESTRequest1'); if cmp is TRESTRequest then begin Memo1.Lines.Add(TRESTRequest(cmp).Params[1].Value); end; end;

A TList<T> is a class, so a variable of type TList<T> being nil is not an empty list, but no list instance at all. In contrast to nil, an existing TList<T> instance can be filled. For nil you first have to create with TList<T>.Create to get a list you can work with. In contrast to that an array is not class.

That is intended. The LSP processes build their own internal data structures decoupled from the BDS ones. The sizes required depend on the complexity of your projects.

In line TImageCollectionSourceItem.Create there is just a call to TWICImage.Create, which initiates a COM call CoCreateInstance. Perhaps there is something wrong with the specific combase.dll on that machine (faulty version, corrupted, infected).

That is not quite right. It handles some non-Integer data types and try to convert the value to Integer. Here are some common examples: function TStringField.GetAsInteger: Integer; begin Result := StrToInt(GetAsString); end; function TFloatField.GetAsInteger: Integer; begin Result := Integer(Round(GetAsFloat)); end; function TMemoField.GetAsInteger: Integer; begin Result := StrToInt(GetAsString); end;