Lajos Juhász

I did it in previous versions mostly XE5 and D2007 and always you have to change dfm then pas can be done by delphi.

In which version of Delphi? For me the IDE want to keep the class from the dfm. What's working for me is to select View as text to show the dfm (alt+f12) change the class for components and then switch back to pas and save the file then will Delphi ask to change the pas. A bit faster solution is to use refind with rules #migrate. Of couse you have to add dataset, datafield, valuechecked and valueunchecked properties.

Another options is to use FireDAC, Ole Automation or library to read xlsx files directly for example TMS Flexcel.

Why are you using WrieString / ReadString. It would be better: Myinifile.WriteInteger('LastDiskSkin', SkinFile, lst1.ItemIndex.ToString); lst1.ItemIndex :=Myinifile.ReadInteger('LastDiskSkin',SkinFile, -1); // or some default index.

I got one when commenting on this forum open an RSP ticket. (Edit. My current bug that I am unable to create a test case is when frame is marked as object instead of inline in the DFM. )

I got using Delphi 11.2 and build all: [dcc32 Fatal Error] F2084 Internal Error: AV7B7C4E22(7B730000)-R00000010-0

It's the name (and maybe even the username?), I guess HDD serial and some other information serials from the machine.

Unfortunately this is a known fact.

Another question is what is a Websocket server? Last time I checked websocket was a protocol.

Is it just me or D11.1 update 1 has a problem debugging a runtime package? I was changing/debugging the core runtime package for the application. The workflow was the folowing: 1.) compile the package, 2.) run the package inside a host application. 3.) Make change 4.) Restart the IDE. Without step 4 I would get instantly internal error.

That is the CPU view, the call stack is on the left side. It should contain something like this: :76f010cc win32u.NtUserWaitMessage + 0xc :00b4ab5e TApplication.Idle + $14E Vcl.Forms.TApplication.HandleMessage Vcl.Forms.TCustomForm.ShowModal mainrm.TForm1.Button1Click($3417030) Vcl.Controls.TControl.Click Vcl.StdCtrls.TCustomButton.Click Vcl.StdCtrls.TCustomButton.CNCommand(???) ...... Most probably the call stack will be empty, in which case open the threads windows with CTRL + ALT + T and select the first thread on the list.

It should be simply a build for every application. So far I have no choice as with every version some bugs are fixed and new are introduced that forces to move to even newer version and hope that (n+1)! will be stable for the applications I am working on. (For me it's easier as application on D11 are still in release candidates. New versions while the stable versions are compiled with XE5.)

It should be compatible, there are some corner cases where it is not. After update you should recompile everything (bpl+exe) just to be sure.

I didn't saw this one. On the other hand lately I mostly do debugging and doesn't create a lot of new forms.

It's strange it's closed as duplicate without the number of the other RSP. We don't know what is in the other RSP and its status.

In this case I would go with Form.CurrentPPI (Every control has a CurrentPPI property).

It's not a good idea to use Screen.PixelsPerInch, with per-monitor DPI it will not work correctly on multi monitor setup with different dpi.

I bet that he wants the call stack for exceptions. (Maybe for multi-platform application. I am guessing, that could be a reason to choose fmx forum as it's the multi platform framework).

In the C# everything is a parameter (https://blog.ultramsg.com/send-whatsapp-message-by-whatsapp-api-c-sharp): procedure TForm1.Button6Click(Sender: TObject); var byte1: TBytes; file2: string; base64: TBase64Encoding; begin if OpenDialog1.Execute then begin /// / begin encodein base64 byte1 := System.iOUtils.TFile.ReadAllBytes(OpenDialog1.FileName); base64 := TBase64Encoding.Create(0); // CharsPerLine = 0 means no line breaks try file2 := base64.EncodeBytesToString(byte1); finally base64.Free; end; var Client := TRESTClient.Create('https://api.ultramsg.com/instance16802/messages/image'); var request := TRESTRequest.Create(nil); var esponse := TRESTResponse.Create(nil); request.Client := Client; request.Response := esponse; Client.ContentType := 'application/x-www-form-urlencoded'; request.Method := TRESTRequestMethod.rmpost; request.AddParameter('token', token_txt.text); request.AddParameter('to', send_to_txt.text); request.AddParameter('image', file2); // request.AddBody(LJSONObject); request.Execute; Memo1.Text := request.Response.Content; end; end;

// CharsPerLine = 0 means no line breaks

Why is file2 a widestring? You should try: procedure TForm1.Button1Click(Sender: TObject); var byte1: TBytes; file2: string; LJSONObject: TJSONObject; base64: TBase64Encoding; begin if OpenDialog1.Execute then begin /// / begin encodein base64 byte1 := System.iOUtils.TFile.ReadAllBytes(OpenDialog1.FileName); base64 := TBase64Encoding.Create(0); // CharsPerLine = 0 means no line breaks try file2 := TNetEncoding.base64.EncodeBytesToString(byte1); finally base64.Free; end; var Client := TRESTClient.Create('https://api.ultramsg.com/instance16802/messages/image'); var request := TRESTRequest.Create(nil); var esponse := TRESTResponse.Create(nil); request.Client := Client; request.Response := esponse; Client.ContentType := 'application/x-www-form-urlencoded'; request.Method := TRESTRequestMethod.rmPOST; LJSONObject := TJSONObject.Create(); try LJSONObject.AddPair('token', 'xxxxxx'); LJSONObject.AddPair('to', '+00000000'); LJSONObject.AddPair('image', file2); request.AddBody(LJSONObject); request.Execute; Memo1.Text := request.Response.Content; finally LJSONObject.Free; end; end; end;

MyCariable:=trunc(MyCariable*100)/100;

This was correct until Delphi 10.4 when ARC ( Automatic Reference Counting) was removed. Now you code the same way on all of the platforms and have to call free or if you must call freeAndNil (freeAndNil is in 99.999999999999999999% a code smell.)

He also mentioned that there are some corner cases where it's not and he believes that we should not have those cases. Best is to recompile everything.

This logic most probably belongs to the field's onchange.